When rsync starts I get the following messages in my log file
Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync: bind failed on port 873
Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync error: error in socket IO (code
10) at socket.c(361)
Anybody know what might be causing this?
David
Almost certainly, something is already using port 873 - probably a
previous invocation of rsync --daemon, or you have inetd listening to it
already.
On a commandline invocation, rsync forks, so invoking it twice in a row
without killing the first one or having the first one die, makes the
Hello,
The attached patch should fix Debian bug #128632
(http://bugs.debian.org/128632). This bug happened because if an error
occurred in writefd_unbuffered (such as the remote end closing the
socket), it would call rprintf, which would call io_multiplexing_write,
which would in turn call
Well, there you go. rsyncd is already set up on your system. You don't
run rsync, inetd does. The way it's set up makes it nice for testing,
too, as you just edit the conf file and test it.
If this is, in fact, another installation of rsyncd, which you shouldn't
mess with, you'll have to
On Fri, Jan 11, 2002 at 08:14:23AM +0100, Laurent CREPET wrote:
I've just upgraded my rsync server to 2.5.1 (before, I was using 2.4.6),
without changing anything in /etc/rsyncd.conf, and now, I have this logs
each time a client connect to server:
2002/01/07 18:33:03 [10432] rsync: reverse
Message: 5
To: [EMAIL PROTECTED]
Subject: how fast should rsync be?
Date: Fri, 11 Jan 2002 17:14:06 +1100 (EST)
From: [EMAIL PROTECTED] (Martin Pool)
People often report rsync taking several hours to transfer last
filesystems, and want to know whether there is anything they can do to
