DO NOT REPLY [Bug 3461] rsync is not atomic when temp-dir is on different device

https://bugzilla.samba.org/show_bug.cgi?id=3461 --- Comment #3 from [EMAIL PROTECTED] 2006-01-28 18:27 MST --- Hmmm. It's true that rsync interleaves memory-mapped reads from the basis file and writes to the temporary file. A smart disk scheduler should avoid making the head dart ba

DO NOT REPLY [Bug 3444] Deal with case-insensitive file-systems better (perhaps by adding an option)

https://bugzilla.samba.org/show_bug.cgi?id=3444 [EMAIL PROTECTED] changed: What|Removed |Added Severity|critical|enhancement Status|NEW

DO NOT REPLY [Bug 2868] Allow fifos to be copied by normal users

https://bugzilla.samba.org/show_bug.cgi?id=2868 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 3277] [Feature req] "I couldn't do something you asked" warning

https://bugzilla.samba.org/show_bug.cgi?id=3277 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |enhancement Status|ASSIGNED

DO NOT REPLY [Bug 3430] Error with ACL-patch and -x on mountpoint

https://bugzilla.samba.org/show_bug.cgi?id=3430 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 2240] Add last-match/short-circuit processing of include/exclude

https://bugzilla.samba.org/show_bug.cgi?id=2240 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 3461] rsync is not atomic when temp-dir is on different device

https://bugzilla.samba.org/show_bug.cgi?id=3461 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #4 from [EM

DO NOT REPLY [Bug 3461] rsync is not atomic when temp-dir is on different device

https://bugzilla.samba.org/show_bug.cgi?id=3461 --- Comment #5 from [EMAIL PROTECTED] 2006-01-29 02:04 MST --- Created an attachment (id=1712) --> (https://bugzilla.samba.org/attachment.cgi?id=1712&action=view) Make the --partial-dir get used when copying As mentioned, if --temp-dir

DO NOT REPLY [Bug 3461] rsync is not atomic when temp-dir is on different device

https://bugzilla.samba.org/show_bug.cgi?id=3461 --- Comment #6 from [EMAIL PROTECTED] 2006-01-29 03:30 MST --- The traditional use of --temp-dir (I think) is for situations when the receiving partition does not have enough free space to accomodate a temporary copy of a large file. Th

DO NOT REPLY [Bug 3277] [Feature req] "I couldn't do something you asked" warning

https://bugzilla.samba.org/show_bug.cgi?id=3277 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #5

DO NOT REPLY [Bug 3461] rsync is not atomic when temp-dir is on different device

https://bugzilla.samba.org/show_bug.cgi?id=3461 --- Comment #7 from [EMAIL PROTECTED] 2006-01-29 14:17 MST --- (In reply to comment #6) > The traditional use of --temp-dir (I think) is for situations when the > receiving partition does not have enough free space to accomodate a tempor

DO NOT REPLY [Bug 3277] [Feature req] "I couldn't do something you asked" warning

https://bugzilla.samba.org/show_bug.cgi?id=3277 --- Comment #6 from [EMAIL PROTECTED] 2006-01-30 11:56 MST --- (In reply to comment #5) > In fact, would anyone object if the non-root meaning of -a changed > to behavior #3? Yes -- I would. I do a lot of copying where I want the perm

DO NOT REPLY [Bug 3277] [Feature req] "I couldn't do something you asked" warning

https://bugzilla.samba.org/show_bug.cgi?id=3277 --- Comment #7 from [EMAIL PROTECTED] 2006-01-30 14:36 MST --- (In reply to comment #6) > Yes -- I would. I do a lot of copying where I want the permissions and groups > copied exactly from the source. If you care about the permissions

DO NOT REPLY [Bug 3277] [Feature req] "I couldn't do something you asked" warning

https://bugzilla.samba.org/show_bug.cgi?id=3277 --- Comment #8 from [EMAIL PROTECTED] 2006-01-30 15:12 MST --- This is not really the place to hold a tangent conversatation, but no, I don't want behavior #2, as I'm not running as root (but I do have multiple groups associated with my

DO NOT REPLY [Bug 3465] New: --files-from does not --delete

https://bugzilla.samba.org/show_bug.cgi?id=3465 Summary: --files-from does not --delete Product: rsync Version: 2.6.6 Platform: Other OS/Version: AIX Status: NEW Severity: normal Priority: P3 Component: cor

DO NOT REPLY [Bug 3465] --files-from does not --delete

https://bugzilla.samba.org/show_bug.cgi?id=3465 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |enhancement Status|NEW

DO NOT REPLY [Bug 3277] [Feature req] "I couldn't do something you asked" warning

https://bugzilla.samba.org/show_bug.cgi?id=3277 --- Comment #9 from [EMAIL PROTECTED] 2006-01-30 16:31 MST --- I'm sorry for abusing your Bugzilla. Let the discussion continue on the mailing list if necessary. Never mind changing the behavior of -a, but an official alias for -rltE -

DO NOT REPLY [Bug 3444] Deal with case-insensitive file-systems better (perhaps by adding an option)

https://bugzilla.samba.org/show_bug.cgi?id=3444 --- Comment #3 from [EMAIL PROTECTED] 2006-01-31 08:16 MST --- > Note that the patch that came > with 2.6.6 builds, but is ineffective. The version in CVS should be OK. Do you mean that the ignore-case.diff patch that is found in the pa

DO NOT REPLY [Bug 3465] --files-from does not --delete

https://bugzilla.samba.org/show_bug.cgi?id=3465 --- Comment #2 from [EMAIL PROTECTED] 2006-01-31 09:13 MST --- Another work around might be to allow a --max-size of zero combined with a --delete. --maxsize of zero is not supported in rsync. While it wouldn't completely solve the origi

DO NOT REPLY [Bug 3444] Deal with case-insensitive file-systems better (perhaps by adding an option)

https://bugzilla.samba.org/show_bug.cgi?id=3444 --- Comment #4 from [EMAIL PROTECTED] 2006-01-31 10:34 MST --- (In reply to comment #3) > Do you mean that the ignore-case.diff patch that is found in the patches > directory of the 2.6.6 source distribution does not work ? That's right

DO NOT REPLY [Bug 3461] rsync is not atomic when temp-dir is on different device

https://bugzilla.samba.org/show_bug.cgi?id=3461 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 3465] --files-from does not --delete

https://bugzilla.samba.org/show_bug.cgi?id=3465 --- Comment #3 from [EMAIL PROTECTED] 2006-01-31 11:13 MST --- (In reply to comment #2) > Another work around might be to allow a --max-size of zero combined with a > --delete. The recommended way to ask rsync to only delete files is to

DO NOT REPLY [Bug 3444] Deal with case-insensitive file-systems better (perhaps by adding an option)

https://bugzilla.samba.org/show_bug.cgi?id=3444 --- Comment #5 from [EMAIL PROTECTED] 2006-02-01 02:46 MST --- --ignore-case solves the critical problem of unwanted file deletions. There still is a (less critical) problem when one want to change the case of a file name. Even on case

DO NOT REPLY [Bug 3271] Rsync instances stay in memory when using in daemon mode

https://bugzilla.samba.org/show_bug.cgi?id=3271 --- Comment #11 from [EMAIL PROTECTED] 2006-02-01 12:53 MST --- Sorry for forgetting to get back to this bug for so long. I've finally analyzed the strace output, and it shows that the generator received an error about the socket closin

DO NOT REPLY [Bug 2499] rsync fails to exit when run from an environment with a signal mask

https://bugzilla.samba.org/show_bug.cgi?id=2499 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 3147] message 'copying unsafe symlink' only appears if verbose>=2

https://bugzilla.samba.org/show_bug.cgi?id=3147 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 3241] Multiple source to dest transfers in one invocation (to same host)

https://bugzilla.samba.org/show_bug.cgi?id=3241 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 2570] cygwin version of rsync produces "Fatal exception 0E in VXD IFSMGR(04)" on Windows 98 SE

https://bugzilla.samba.org/show_bug.cgi?id=2570 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 3479] New: Request: timestamps in --log-format

https://bugzilla.samba.org/show_bug.cgi?id=3479 Summary: Request: timestamps in --log-format Product: rsync Version: 2.6.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Compone

DO NOT REPLY [Bug 3479] Request: timestamps in --log-format

https://bugzilla.samba.org/show_bug.cgi?id=3479 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |enhancement Status|NEW

DO NOT REPLY [Bug 3304] on --delay-updates remove .~tmp~ recursively

https://bugzilla.samba.org/show_bug.cgi?id=3304 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 2793] xattr support fails with multiples attributes

https://bugzilla.samba.org/show_bug.cgi?id=2793 --- Comment #1 from [EMAIL PROTECTED] 2006-02-04 21:09 MST --- I can't reproduce this with CVS rsync. I made test_pierre/test.file with the given attributes and values. When I made a copy of test_pierre, the attributes were synchronize

DO NOT REPLY [Bug 3485] New: rsync uses more space in destination even with -S specified

https://bugzilla.samba.org/show_bug.cgi?id=3485 Summary: rsync uses more space in destination even with -S specified Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Linux Status: NEW Severity: majo

DO NOT REPLY [Bug 3485] rsync uses more space in destination even with -S specified

https://bugzilla.samba.org/show_bug.cgi?id=3485 --- Comment #1 from [EMAIL PROTECTED] 2006-02-05 13:05 MST --- Does the source tree contains hard-linked files? If so, has -H rsync option been used? cp -a would preserve hard links. -- Configure bugmail: https://bugzilla.samba.org/us

DO NOT REPLY [Bug 3485] rsync uses more space in destination even with -S specified

https://bugzilla.samba.org/show_bug.cgi?id=3485 --- Comment #2 from [EMAIL PROTECTED] 2006-02-06 04:21 MST --- (In reply to comment #1) > Does the source tree contains hard-linked files? > If so, has -H rsync option been used? > cp -a would preserve hard links. > Yes, the command wa

DO NOT REPLY [Bug 3299] rsync: now replaces non-ASCII character with numerical values

https://bugzilla.samba.org/show_bug.cgi?id=3299 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 3488] New: writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32)

https://bugzilla.samba.org/show_bug.cgi?id=3488 Summary: writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32) Product: rsync Version: 2.6.6 Platform: Sparc OS/Version: Solaris

DO NOT REPLY [Bug 3488] writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32)

https://bugzilla.samba.org/show_bug.cgi?id=3488 --- Comment #1 from [EMAIL PROTECTED] 2006-02-06 12:23 MST --- Created an attachment (id=1722) --> (https://bugzilla.samba.org/attachment.cgi?id=1722&action=view) Truss output. -- Configure bugmail: https://bugzilla.samba.org/userpre

DO NOT REPLY [Bug 3485] rsync uses more space in destination even with -S specified

https://bugzilla.samba.org/show_bug.cgi?id=3485 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #3 from [EM

DO NOT REPLY [Bug 3488] writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32)

https://bugzilla.samba.org/show_bug.cgi?id=3488 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #2 from [EM

DO NOT REPLY [Bug 3488] writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32)

https://bugzilla.samba.org/show_bug.cgi?id=3488 --- Comment #3 from [EMAIL PROTECTED] 2006-02-06 15:09 MST --- >I'm assuming by "hung" you mean more of a "hang up", as in problem-causing item >where rsync died, rather than "hung" as in the process keeps running but stops >doing anyth

DO NOT REPLY [Bug 3299] rsync: now replaces non-ASCII character with numerical values

https://bugzilla.samba.org/show_bug.cgi?id=3299 --- Comment #3 from [EMAIL PROTECTED] 2006-02-07 05:33 MST --- I should also mention that there is now an option that tells rsync that you want it to pass through all high-bit characers unescaped (instead of trying to escape only the inv

DO NOT REPLY [Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #4 from [EMAIL PROTECTED] 2006-02-07 07:25 MST --- There is now a patch named detect_renamed.diff in the patches dir that implements the basics of finding renamed files. This will probably go onto the trunk for the release a

DO NOT REPLY [Bug 3491] New: throttle disk IO during filelist/directory parsing

https://bugzilla.samba.org/show_bug.cgi?id=3491 Summary: throttle disk IO during filelist/directory parsing Product: rsync Version: 2.6.4 Platform: All URL: http://vilius.multiply.com/video/item/10 OS/Version: Linux Stat

DO NOT REPLY [Bug 3491] throttle disk IO during filelist/directory parsing

https://bugzilla.samba.org/show_bug.cgi?id=3491 --- Comment #1 from [EMAIL PROTECTED] 2006-02-08 02:22 MST --- I like this idea. I, too, have seen degradation in response times when rsync starts on a large hierarchy. Using nice didn't help (much). Wouldn't it be better to count up

DO NOT REPLY [Bug 3492] New: rsync: connection unexpectedly closed (24 bytes read so far)

https://bugzilla.samba.org/show_bug.cgi?id=3492 Summary: rsync: connection unexpectedly closed (24 bytes read so far) Product: rsync Version: 2.6.7 Platform: Other OS/Version: HP-UX Status: NEW Severity: n

DO NOT REPLY [Bug 3488] writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32)

https://bugzilla.samba.org/show_bug.cgi?id=3488 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 3492] rsync: connection unexpectedly closed (24 bytes read so far)

https://bugzilla.samba.org/show_bug.cgi?id=3492 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from [EM

<    1   2