Re: strip setuid/setgid bits on backup (was Re: small security-related rsync extension)
never seen a file created with a newline in the filename (except, perhaps as a test). The newline in filename issue And in security exploits :-) Given a newline-based format, one *must* quote or deny newlines in filenames, not assume they're rare. (No obvious reason not to use URL-style %-quoting, or mime-style =-quoting, if you want to preserve ease of filtering...) -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Status Query - Please respond - Re: Patch to avoid 'Connection reset by peer' error for rsync on cygwin
Just because Linux lets you get away without it doesn't mean its a good idea. Except this has nothing to do with linux - this is unix behaviour that goes all the way back, it's part of the process model. It's part of what exiting *does*, so it *is* a bug in cygwin if it isn't doing the cleanup (and really, cygwin does so many other bizarre things under the covers to create Unix/POSIX semantics in the Very Different win32 environment, I'm more than a little surprised it isn't doing this already... skeptical, even, though I haven't been deep inside cygwin in years.) -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: [PATCH] --soften-links option (fwd from md@Linux.IT) Re: rsync and debian mirrors
May i suggest this be more clear, along the lines of Convert a hard link to a symbolic link if on the destination it would have to span filesystems Along with a Except that's overly precise -- for example, AFS doesn't permit hard links to span *directories* even if they're on the same volume. Though it does still give EXDEV as the error in that case, so maybe it won't actually confuse anyone... -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: (fwd from uke@jeremy.org) thanks and patch
Wouldn't using detached signatures make more sense for this application? -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: relationship counselling for debian and rsync
It would be pretty cool if I could be automatically cc'd on Debian bug reports about rsync, if the BTS supports that. I'm pretty sure this got added in the last month or two... (type type type google google google) Ah yes, this posting to the debian QA list: | You can (un)subscribe to a package by sending a mail to | [EMAIL PROTECTED] The possible commands are : | subscribe srcpackage | subscribe srcpackage email | unsubscribe srcpackage | unsubscribe srcpackage email | quit | | This part does work and is ready (a bit of testing is always | appreciated though). Once you're subscribed you get | the mails sent to srcpackage@packages.qa.debian.org (the BTS will be | modified to send mails to this adress at the same time it sends mails | to the maintainer). The mails sent have an header (X-Loop: | srcpkg@packages.qa.debian.org) that lets you easily filter it | in a special mailbox if needed. Hope this helps... _Mark_ [EMAIL PROTECTED] The Herd of Kittens Debian Package Maintainer -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: move rsync development tree to BitKeeper?
GNU Subversions is apparently now self-hosting (and is actually free, instead of arguably free :-) If you're looking at perforce or bitkeeper, though, also look at Accurev 3.0 (which is free-for-free-software, in java, *fast* and has a better consistency model...)
Re: Using rsync 2.3.1, individual file size limitation...
send_files failed to open .../data1/intlmv.data/histimv.rec: Value too large for defined data type Is that Solaris 8? I ask not just because you should have mentioned this in the bug report (tsk tsk :-) but that I've seen that error and it *didn't* have anything to do with file size (or rsync) but instead had to do with files having negative timestamps - often created by unzip. Just something to keep in mind, when resubmitting your question with enough information to actually make sense of it...
