From: Dr. Martin Körfer (koerfer@mpch-mainz.mpg.de)
Date: Mon Jan 31 2005 - 04:04:17 EST
Hi managers,
thanks for the extensive and (like most times) exhaustive answers to my problem
below.
Dr. Tom Blinn gave me a genaeral advice how to hnadle problems if the error
"failed to exec" occurs;
others pointed out that the appropriate path was not found;
Tim Cutts, Martin Adolfsson, Warren Sturm told me to use the "-e" or "-rsh" -
option of the rsync-command, what at least solved the problem.
Shame on me: I should have read the "fucking man-page" a bit more carefully !
Martin
----------------------------------
Original question:
Having successfully installed rsync on Tru64 5.1a, I was able to synchronize the
data on our anonymous ftp-server with a disk on an "access-server for
users"
All worked fine if I typed in as root (form the access-server):
/usr/bin/rsync -av --delete ftp:/ftp/pub /ftp
The ftp-disks were synchronized by using "key-login" for root through "ssh2"
running on both servers.
Now putting this into the the crontab-file, execution failed with the
error-message:
rsync: Failed to exec ssh: No such file or directory (2)
even putting the command into a script-file with the preceding lines:
#!/bin/csh
source /.cshrc
(csh is the root-login-shell and the /usr/bin-path is defined in /.cshrc)
results in the same error.
Any idea how to run rsync thb in the "crontab" ???
Thanks
Martin
-------------------------------------------------
This mail sent through IMP: webmail.mpch-mainz.mpg.de
-------------------------------------------------
This mail sent through IMP: webmail.mpch-mainz.mpg.de
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:14 EDT