I'm checking into the innards of rsync in order to try to figure out the
best way to add a proper move-files option, and I think I discovered a
potential hang when sending large numbers of files between systems. If
I understand this correctly from my preliminary reading of the code, the
The unexpected EOF in read_timeout can happen for a variety of reasons,
but it typically shows up when you have deadlock (no bytes sent across
the wire, which could happen as a result of ssh blocking for instance)
or a very large filesystem being syncronized (which could happen if the
This is the umpteenth time I've heard it mentioned that rsync builds a list
of all the files it needs to transfer in memory, and that this can cause
rsync to actually run out of memory when dealing with large numbers of
files. Why in god's name does it do this? Surely it could do all it has to
John == John L Allen Allen writes:
John But I do agree it would be nice if the man page documented
John them.
Or, better still, if rsync itself simply told you what they meant ;-)
--- log.c.orig Sat Jan 29 06:35:03 2000
+++ log.c Wed Oct 18 14:01:26 2000
@@ -25,6 +25,29 @@
On Tue, May 29, 2001 at 11:36:11AM -0400, Tuc wrote:
I don't have any experience with BSDI, but what's the full command line of
the rsync command you're trying to run?
/usr/local/bin/rsync -vrlptgozx --partial --delete --force
--rsync-path=/usr/local/bin/rsync --exclude='stats/'
Thank you very much this is a very plausiable cause.
It is a very large filesystem. thanks again.
--- Alberto Accomazzi [EMAIL PROTECTED] wrote:
The unexpected EOF in read_timeout can happen for a
variety of reasons,
but it typically shows up when you have deadlock (no
bytes sent across
On Tue, May 29, 2001 at 12:02:41PM -0500, Phil Howard wrote:
Dave Dykstra wrote:
On Fri, May 25, 2001 at 02:19:59PM -0500, Dave Dykstra wrote:
...
Use the -W option to disable the rsync algorithm. We really ought to make
that the default when both the source and destination are
On Wed, May 30, 2001 at 02:05:33AM -0500, Phil Howard wrote:
I'm a novice at rsync, so I can't tell you all the details, but, in
general, the unexpected EOF in read_timeout (usually) means that
something not so good happened on the server side. On what server I was
connecting to, I
On Tue, May 29, 2001 at 05:30:13PM -0400, Frank Artusa wrote:
I have a few web servers running Redhat 6.2 which synchronize via two
scripts to an rsync server. They run every 5 and 15 minutes through a cron
job. For many months this worked great until a few days ago when it just
stopped
On Wed, May 30, 2001 at 11:23:56AM -0400, Brian Johnson wrote:
I'm using rsync to backup my main hard drive to a second hard drive.
Although it is currently a local hard drive, I intend to switch to backup to
a remote location.
My question is:
It seems that rsync can compress the data for
On Wed, May 30, 2001 at 10:30:07AM -0400, Neil Schellenberger wrote:
Content-Description: message body text
John == John L Allen Allen writes:
John But I do agree it would be nice if the man page documented
John them.
Or, better still, if rsync itself simply told you what they
Neil Schellenberger [EMAIL PROTECTED] wrote:
...
(e.g. I seem to remember Dave Dykstra mentioning that certain
server errors were not logged to the client for security
reasons - I may have busted that, sorry).
Dave Martin Tridge will need to decide about that patch. I
Hi all,
I continue to have difficulties when attempting to synchronize between two
local directories. One of them is a NetWare volume mounted using NCP. The
catalogue builds and the synchronization of the two directory's starts. For a
reason unknown to me, the process will stop completely
13 matches
Mail list logo
