multiplexing overflow errors

2009-11-27 Thread Dieter Stüken
I'm using rsync 3.0.6 between two solaris 8/10 hosts an I frequently get multiplexing overflow errors: log/20091123_223901/dresden.log:multiplexing overflow 101:7104843 [sender] log/20091123_223901/frankfurt.log:multiplexing overflow 101:7104843 [sender]

Problem with permissions

2009-11-27 Thread Chris Adams
I'm trying to set up a full server backup using rsync 3.0.6. I'm using --fake-super, and SSH keys to access a remote server as a normal user. My problem is that there is a local directory that has permissions 0111 (d--x--x--x), and rsync throws an error trying to set the xattr: rsync: failed to

Re: multiplexing overflow errors

2009-11-27 Thread Wayne Davison
On Fri, Nov 27, 2009 at 7:45 AM, Dieter Stüken d.stue...@conterra.dewrote: log/20091123_223901/dresden.log:multiplexing overflow 101:7104843 [sender] This has come up before. That number translates into the byte sequence 0x4b 0x69 0x6c 0x6c, which is Kill in ASCII. So, something is

Re: multiplexing overflow errors

2009-11-27 Thread Matt McCutchen
On Fri, 2009-11-27 at 10:56 -0800, Wayne Davison wrote: On Fri, Nov 27, 2009 at 7:45 AM, Dieter Stüken d.stue...@conterra.de wrote: log/20091123_223901/dresden.log:multiplexing overflow 101:7104843 [sender] This has come up before. That number translates into the

DO NOT REPLY [Bug 6936] New: rsync silently fails to preserve uid/gid of -1

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6936 Summary: rsync silently fails to preserve uid/gid of -1 Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3

Possibility so that --max-size AFFECTS --delete ?

2009-11-27 Thread Stefan Nowak
Hello rsyncers! PRACTICAL CIRCUMSTANCES: Backup1 shall be identical to Original. My traditional custom. NO HELP NEEDED for this. Backup2 shall only be a subset of the original, only files with a certain maximum size and filename/suffix pattern get included. For this I use rsync's filename

DO NOT REPLY [Bug 4378] Don't delete files that wouldn't have been transferred

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=4378 m...@mattmccutchen.net changed: What|Removed |Added Summary|Don't delete file types that|Don't delete files that

DO NOT REPLY [Bug 4378] Don't delete files that wouldn't have been transferred

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=4378 --- Comment #4 from m...@mattmccutchen.net 2009-11-27 20:34 CST --- (In reply to comment #2) I notice that the patch only affects extraneous special files immediately inside file-list directories, not those in extraneous directories.

DO NOT REPLY [Bug 4378] Don't delete files that wouldn't have been transferred

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=4378 --- Comment #5 from m...@mattmccutchen.net 2009-11-27 20:36 CST --- (In reply to comment #4) The goal of this ticket is really to make --min-size/--max-size behave more like an ordinary exclude. Whoops, the ticket was originally

Re: Possibility so that --max-size AFFECTS --delete ?

2009-11-27 Thread Matt McCutchen
On Sat, 2009-11-28 at 00:06 +0100, Stefan Nowak wrote: Is there a possibility, so that --max-size AFFECTS --delete actually? Situation where it makes sense: Imagine that I had the rule --max- size=1M and my backup-storage is satisfying. But one day it ain't enough anymore, and I decide to

DO NOT REPLY [Bug 5795] look into a improved tear-down processing during fatal errors

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=5795 --- Comment #5 from m...@mattmccutchen.net 2009-11-27 20:45 CST --- This is fixed in the current development rsync, right? When it gets an error writing to the socket, it continues to read for messages from the other side. --

Re: Possibility so that --max-size AFFECTS --delete ?

2009-11-27 Thread Stefan Nowak
Hi! On 2009-11-28 at 03:43 +0100 Matt McCutchen wrote: On Sat, 2009-11-28 at 00:06 +0100, Stefan Nowak wrote: Is there a possibility, so that --max-size AFFECTS --delete actually? Situation where it makes sense: Imagine that I had the rule --max- size=1M and my backup-storage is satisfying.

Does --archive include an --update behaviour?

2009-11-27 Thread Stefan Nowak
Manpage of rsync 3.0.6 about option --update: [...] This forces rsync to skip any files which exist on the destination and have a modified time that is newer than the source file. [...] Here the manpage is very clear to me! But if I don't use that option: Would rsync overwrite newer files at

Re: Possibility so that --max-size AFFECTS --delete ?

2009-11-27 Thread Matt McCutchen
On Sat, 2009-11-28 at 05:15 +0100, Stefan Nowak wrote: On 2009-11-28 at 03:43 +0100 Matt McCutchen wrote: On Sat, 2009-11-28 at 00:06 +0100, Stefan Nowak wrote: The content of this newsgroup post, makes me think, that in earlier versions --max-size may have once AFFECTED --delete:

Re: Does --archive include an --update behaviour?

2009-11-27 Thread Matt McCutchen
On Sat, 2009-11-28 at 05:30 +0100, Stefan Nowak wrote: Manpage of rsync 3.0.6 about option --update: [...] This forces rsync to skip any files which exist on the destination and have a modified time that is newer than the source file. [...] Here the manpage is very clear to me! But if I

DO NOT REPLY [Bug 6928] Warn the user to use --modify-window=1 --no-owner --no-group etc. on FAT partitions

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6928 --- Comment #1 from m...@mattmccutchen.net 2009-11-27 22:51 CST --- I would be disinclined to add this to the main version of rsync. Rsync generally doesn't devote effort to second-guessing the user. Not reading the man page is not a

RE: rsync of STDIN to a file.

2009-11-27 Thread Matt McCutchen
On Wed, 2009-11-25 at 12:09 +, Mark Young wrote: I believe the rdiff man page is still not correct, even with your submitted changes. It states In every case where a filename must be specified, - may be used instead to mean either standard input or standard output as appropriate.. I've

DO NOT REPLY [Bug 6916] Avoid bundling a modified zlib

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6916 --- Comment #2 from m...@mattmccutchen.net 2009-11-27 23:57 CST --- (In reply to comment #1) The only thing for rsync to potentially do is to have a build option for using a compatible, shared zlib. What happened to, Tridge has

DO NOT REPLY [Bug 6927] Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc.

2009-11-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6927 --- Comment #2 from m...@mattmccutchen.net 2009-11-28 00:20 CST --- This could probably be implemented as a popt alias rather than in the rsync program itself. Some specific comments: (In reply to comment #0) * Maybe it should also