rsync server-client users

tim.conway at tim.conway at
Tue Sep 17 00:30:01 EST 2002

Such behaviour has been seen.  In some iterations of rsync, running from 
cron, on some systems, it would detect STDIO as a socket and try to run as 
a daemon.  I don't know when that was, or what platforms, but your version 
is way downlevel.  There are a lot of reasons that the current version is 
2.5.5, and reliablilty issues are among them.  See how it looks with BOTH 
ENDS running a current version of the utility.

Good luck.

Tim Conway
tim.conway at
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"

Robert Brooks <rbrooks at>
Sent by: rsync-admin at
09/16/2002 03:25 PM

        To:     rsync at
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        rsync server-client users

Subject: rsync client-server users

Are you using  rsync  in a client-server

If you are, and if you have set up your
cron or anacron tables to run an rsync
client, does the client ever just hang?

I am running one rsync server and two
rsync clients, both clients are under
control of anacron.  And they both hang
on the rsync command, forever.

All three systems run Red Hat 7.1 and
rsync 2.4.6-2.  No data is ever sent
from the client.  In other words, it's
not a premature End-of-File condition.
And, after the hung tasks are killed,
I can run the scripts directly from root
without any error whatsoever.

And the failure isn't intermittent, it
happens every time the backup script is
run by anacron.  Yet the same script
always succeeds when run at the root console.

One at a time, I have added these options
to the rsync command:


Finally, I redirected the output of the
rsync command with

  > /tmp/rsync.txt

Nothing changed, no data was ever sent to
the rsync server.

Next, I took a snapshot of all the open files
just before the backup script was started, and
a snapshot of the open files during the 60-second
interval when the rsync command was timing out.
But, I can't tell from the differences between
the two snapshots what is going on for sure.

After not having any backup for any of my
computers, I was looking at rsync as a way
of providing automatic daily, weekly, monthly,
etc., backup.  But since it fails when running
under control of anacron, I'll have to keep
looking for some backup package that will
support automated, unattended operation.

To unsubscribe or change options:
Before posting, read:

More information about the rsync mailing list