(Yucky html mail formatting, by the way)
running from cron, rsync sometimes interprets stdin as a socket, which it
takes to mean that it is being run from inetd, and should run in daemon
mode. I think that's fixed in more recent versions, but i don't know
the
history or theory. best fix is to redirect all three filehandles.
There's been a lot of time passed since your question, so i'm going
ahead
an answering. Expect corrections.
Tim Conway
tim.conway@philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me.... Tim?"
"Jiri Cvrk" <cvrk@mbox.dkm.cz>
Sent by: rsync-admin@lists.samba.org
05/10/2002 05:16 AM
To: <rsync@lists.samba.org>
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: rsync & cron
Classification:
hello,
when I use rsync from commandline (RH 7.2, ssh2), it works fine.
rsync -e ssh -a -v zaloha@192.168.2.100:/home/samba/m/aaa.txt /home/m/aaa.txt
but when I try to use it in crontab such as
33 11 * * * rsync -e ssh -a -v zaloha@192.168.2.100:/home/samba/m/aaa.txt
/home/m/aaa.txt
</dev/null
or
33 11 * * * rsync -e ssh -a -v zaloha@192.168.2.100:/home/samba/m/aaa.txt
/home/m/aaa.txt
I have also tried this rsync command in script.. and always I get the
following.
Aborted by user!
unexpected EOF in read_timeout.
What should be wrong?
Thank you for any help.
--
Jiri Cvrk (CZ)
http://digital.zde.cz