Please explain "Export Path (both local and ftp)"

[rcane]

I have been searching for the documentation on how to fill out the "Export Path (both local and ftp)" field and I am at a loss.

my question is
do i place the full server path to the remote directory i wish to upload my export to in this field? i am confused by the wording "both local and ftp" It sounds like you have to have identical file structures on the remote and local machines in order to ftp your export? but i have tried everything i can think of and that does not appear to be the case.

My export seems to be running fine, i can watch it rebuild a directory called /cacti-ftp-temp/ in the root of the local server, but I never get the files to ftp to the remote directory i have specified in the "Export Path" field. I can manually ftp the files over to the remote server with a SSH command line but cacti does not appear to do this automatically as i would like.

I viewed the logs and see where it says the php process to transfer files has started but i dont see any errors after that to indicate the transfer failed. any help would be greatly apreciated.

[daemon]

if you want it to FTP, you need to do two things. first, choose one of the FTP options instead of classic ("use PHP functions" would be a good start). then, specify the FTP information below. make sure you can do a manual FTP using the same options to be sure that it works right first. that should get you where you want to be.

[TheWitness]

The Export functions are being re-tooled right now. Should be done as soon as I get a free 1.5 days to wrap up.

TheWitness

[daemon]

what sort of things do you have planned?

[rcane]

Is their an ETA for this release? I hope soon, Thanks for the help

[TheWitness]

1) Fix export FTP functions
2) Improve the logic for export to be more intellegent, as it can delete things you don't want deleted if you are not careful
3) Allow branches to be exported in tree mode as a sigle tree or as separate tree's
4) Allow a user account to be used instead of the Admin account, so that graph permissions can be applied during export.
5) Improve logging as some was via prints and others were via the logging functions.
6) Eliminate writing a PNG more than once, unless you are using multiple tree export method.

Not soon enough I guess.

TheWitness

[rcane]

sounds great,

I will patiently be awaiting the new release, for now i believe we may just automate a ftp job to move them from one server to tanother but it would be nice to have it all inside the same app.