On Sat, Dec 17, 2005 at 11:22:58PM +, Jamie Lokier wrote:
> rsync: mkstemp "/mnt/storage/bin/" failed: Success (0)
That makes me wonder if the thread handling is not properly giving
each thread its own errno.
> ./rsync: io.c: 334: push_redo_num: Assertion `am_receiver()' failed.
That sho
So far I am not having luck with the threads version:
rsync: mkstemp "/mnt/storage/bin/" failed: Success (0)
./rsync: io.c: 334: push_redo_num: Assertion `am_receiver()' failed.
is typical. Or SIGSEGV. There is something very fishy going on, and
I suspect it isn't the rsync code, but someth
> On Sat, Dec 17, 2005 at 03:55:27PM -0600, scott wrote:
> > rsync --archive -e '/usr/bin/ssh -p 22' --verbose
> > \ --include-from=/root/my-backupfilter --recursive
> > \ --delete --existing / [EMAIL PROTECTED]:/home/backupdir
> >
> > which is close, but still updates files
>
> You need to also ad
On Sat, Dec 17, 2005 at 03:55:27PM -0600, scott wrote:
> rsync --archive -e '/usr/bin/ssh -p 22' --verbose
> \ --include-from=/root/my-backupfilter --recursive
> \ --delete --existing / [EMAIL PROTECTED]:/home/backupdir
>
> which is close, but still updates files
You need to also add --ignore-exi
I use files-from and want to have rsync connect to my backup server and ONLY
delete the files that are no longer on the source server. If the file which
is in my files-from filter list has changed, i do not wan tit updated. Bu
if the file on the source server has been deleted, I want rsync to (on
Nelson H. F. Beebe dixit:
>List traffic today asks about changing rsync to use lightweight
>threads instead of heavyweight fork.
It's not lightweight on all operating systems.
>Before rushing into building a threads version of rsync
If at all, make it a compile-time option to add thread support
On a Redhat ES 3 system running rsync-2.5.7-5.3E I have a script which
sends files to
other servers. I have noted lately that occasionally rsync will exit
with a code of 0 prematurely.
See below a snippet of the code I am using :
if [ ! -s $file ]
then
# File does not
