I'm new to rsync and I'm trying to use rsync-2.4.6 to sync web content
between 2 AIX (4.3.3.0) boxes (from SERVERA to SERVERB).
I've gone through the man pages for rsync and rsyncd.conf, searched the web
site and browsed several months worth of the mailing list, but I still
can't figure out whic
I have received a few queries regarding my progress in solving the rsync
sender's abortive connection close() on Winsock-based platforms. In my
research, I stumbled across articles that implied that Microsoft is not the
only OS vendor that provides platforms that may exhibit this problem. I am
On Thu, 14 Jun 2001, Wayne Davison wrote:
> Here's a patch.
I forgot to mention that you should run "make proto" after applying that
patch.
..wayne..
On Thu, 14 Jun 2001, Martin Pool wrote:
> I'm slightly concerned that this may cause some other failure modes to
> falsely cause the client to return 0.
I was thinking about this myself. The code sets "eof_error = 0" for any
user of read_line(), and (judging from my quick inspection) this doesn'
Here is Debra Weiss's patch to create rsync+, updated to rsync version 2.4.6
by me. More information about rsync+ can be found at
http://www.ils.unc.edu/i2dsi/unc_rsync+.html
diff -urN rsync-2.4.6/Makefile.in rsync-2.4.6-plus/Makefile.in
--- rsync-2.4.6/Makefile.in Tue Sep 5 19:46:43 2
Tim -
At the suggestion of someone else I've added the 'delaycompress' directive
to the config. This will leave the file uncompressed after moving it and
compress it on the next rotation. Here's my current logrotate stanza:
/var/log/rsyncd.log {
rotate 12
monthly
delaycompres
I would have to disagree with the compress, unless you don't mind losing log
information. It'll compress and unlink the file, and just like a move to a different
filesystem, rsync will keep writing to the log until it closes, at which point,
whatever was
written after the compress is gone.
Ti
On 13 Jun 2001, Scott Russell <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 13, 2001 at 03:54:31PM -0500, Dave Dykstra wrote:
> > On Wed, Jun 13, 2001 at 04:38:52PM -0400, Scott Russell wrote:
> > > David -
> > >
> > > No, no problem, yet. Just trying to avoid problems. :) I think the question
> > > r
On 13 Jun 2001, Wayne Davison <[EMAIL PROTECTED]> wrote:
> The CVS version of rsync outputs an error on exit after listing the
> modules from an rsync daemon (running "rsync host::"). The following
> patch fixes this. (If you haven't applied my "nohang" patch, you'll see
> an offset for this pat
> I'm a little surprised at this. I use rsync on Win2k every day. Runs
> automatically at 1pm in my case, and it hasn't bombed yet. Win2k is the
> "sender", receiver is Linux 2.2.13-0.9. Both have rsync 2.4.6. cygwin is
> a little old on win2k, uname -a returns 1.1.2. Linux is running sshd
>
> When I try to sync using ssh back to the same machine or to another machine,
> the sync always hangs in the same place I've tried syncing various
> directories and each directory always hangs on the same file file in each
> directory...
>
> Any clues?
>
It works for me (just the same enviro
The patch seems to work for me, patching the tar file didn't work ,so i
split the patch into 2 patches then run the patch commands for main.c and
io.c independently.
-Message d'origine-
De : Wayne Davison [mailto:[EMAIL PROTECTED]]
Envoyé : 14 juin, 2001 05:11
À : Wilson, Mark - MST
Cc :
12 matches
Mail list logo
