DO NOT REPLY [Bug 3752] rsync unusable with EncFS filesystem

2009-05-03 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3752 --- Comment #4 from miche...@jacey.org 2009-05-03 11:44 CST --- (In reply to comment #2) The problem is indeed with EncFS/FUSE... e.g mv xxx yyy changes the mod time Solved by modifying syscall.c int do_rename(const char

DO NOT REPLY [Bug 3752] rsync unusable with EncFS filesystem

2009-05-03 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3752 way...@samba.org changed: What|Removed |Added Status|CLOSED |REOPENED Resolution|FIXED

DO NOT REPLY [Bug 3752] rsync unusable with EncFS filesystem

2009-05-03 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3752 way...@samba.org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|

DO NOT REPLY [Bug 3752] rsync unusable with EncFS filesystem

2006-05-05 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3752 --- Comment #1 from [EMAIL PROTECTED] 2006-05-05 01:28 MST --- After rsync sets the time/attributes on a file, it renames the file into place and it is done with it. If the timestamp is changing after that, I have a hard time imaging

DO NOT REPLY [Bug 3752] rsync unusable with EncFS filesystem

2006-05-05 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3752 --- Comment #2 from [EMAIL PROTECTED] 2006-05-05 13:39 MST --- The problem is indeed with EncFS/FUSE... e.g mv xxx yyy changes the mod time Solved by modifying syscall.c int do_rename(const char *fname1, const char *fname2) {

DO NOT REPLY [Bug 3752] rsync unusable with EncFS filesystem

2006-05-05 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3752 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|