| 7:17 pm on Nov 30, 2007 (gmt 0)|
try "whereis ftp" to see if there is a path to another version of ftp.
| 8:34 pm on Nov 30, 2007 (gmt 0)|
ftp: /usr/bin/ftp /usr/share/man/man1/ftp.1.gz
when I use the command whereis ftp. So that only found the same version and the gzipped man page.
| 8:36 pm on Nov 30, 2007 (gmt 0)|
try using "whoami" to get the user of the cron job.
then try to run ftp under that user and see results what you get.
| 9:14 pm on Nov 30, 2007 (gmt 0)|
Another tip - you may want to gzip the sql files to make them smaller thus quicker for ftp-ing.
And if you are worried about security look into sftp so that you don't need to transmit unsecure login details.
| 9:19 pm on Nov 30, 2007 (gmt 0)|
In the cron editor I selected to run the job as root. When logged in as root, "ftp -u [IP]" works from the shell.
Just to be sure though, I created a new cron job and selected to run it as root as well. The new cron command was just "whoami" and the output was "root" so I know that the user selection function works at least.
Thanks for your help so far, I really appreciate it!
| 11:00 pm on Nov 30, 2007 (gmt 0)|
try echoing and comparing the PATH variable for both environments.
| 12:53 am on Dec 1, 2007 (gmt 0)|
It *appears*, at least, that you only have one copy of "ftp" on your machine. So, looking at paths is not going to get you anywhere.
To be sure, first make sure your whereis database is up-to-date:
Then run the "whereis" again.
If you still only find one copy, the only thing I can think of is a command alias. Check your .profile, etc.
A good time to inject a bit of finger-wagging: if this is going over the Internet, remember that FTP is insecure. You are much better off using sftp. Then you can also set-up a public-private keypair, and you won't have to stick a password in the script.