On Fri, 2010-08-13 at 14:04 -0400, mike mitchell wrote:
> Hi. I'm having a problem with rsync not deleting subdirectories that
> exist at the destination but which have been removed/renamed on the
> source. I'm running 64-bit Arch, rsync 3.0.7, and am trying to back up
> /home to an external USB dr
On Fri, 2010-08-13 at 11:26 -0400, Brian K. White wrote:
> I have sample data that exposes this repeatably:
> http://lists.samba.org/archive/rsync/2008-October/021889.html
Thanks, but we figured out the problem several months ago and it should
be fixed in rsync 3.0.7:
https://lists.samba.org/arch
On Fri, 2010-08-13 at 15:45 -0400, Vallon, Justin wrote:
> It seems that even if -p (or -a, etc) are not used, permissions are
> still propagated from client to server, though not updated.
Correct. This is a historical behavior inherited from cp that is hardly
ever what you want. See the man pag
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #2 from m...@mattmccutchen.net 2010-08-14 02:19 CST ---
(In reply to comment #0)
> -> symbolic link(s) seems to be recreated/reported as new, why? But only when
> linking to moved/renamed directory.
Is your OS capable of har
https://bugzilla.samba.org/show_bug.cgi?id=7618
the_ma...@seznam.cz changed:
What|Removed |Added
CC||the_ma...@seznam.cz
--- Commen
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #4 from m...@mattmccutchen.net 2010-08-14 02:49 CST ---
(In reply to comment #3)
> (In reply to comment #2)
> > Is your OS capable of hard-linking symlinks? Check the value of
> > CAN_HARDLINK_SYMLINK in config.h when you bu
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #5 from the_ma...@seznam.cz 2010-08-14 04:04 CST ---
(In reply to comment #4)
>
> You can also do the test by hand:
>
> $ ln -s nonexistent broken
> $ ln broken broken2
>
# ln -s nonexistent broken
# ln broken broken2
# l
On Sat, Aug 14, 2010 at 3:04 AM, Matt McCutchen wrote:
> On Fri, 2010-08-13 at 14:04 -0400, mike mitchell wrote:
>> Hi. I'm having a problem with rsync not deleting subdirectories that
>> exist at the destination but which have been removed/renamed on the
>> source. I'm running 64-bit Arch, rsync
On Sat, 2010-08-14 at 06:16 -0400, mike mitchell wrote:
> I wasn't able to reproduce the problem
> from any other source or destination, even in nested subdirectories
> within a directory in my home. It was only when using /home/mike as
> the source, so I guessed there must be something wrong in th
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #6 from m...@mattmccutchen.net 2010-08-14 15:28 CST ---
(In reply to comment #5)
> (In reply to comment #4)
> >
> > You can also do the test by hand:
> >
> > $ ln -s nonexistent broken
> > $ ln broken broken2
> >
>
> # ln
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #7 from the_ma...@seznam.cz 2010-08-14 15:44 CST ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > >
> > > You can also do the test by hand:
> > >
> > > $ ln -s nonexistent broken
> >
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #8 from m...@mattmccutchen.net 2010-08-14 16:11 CST ---
Yes, I was mixed up. A Linux destination should have no trouble hard-linking
symlinks.
New theory: the receiving rsync was configured with HAVE_LUTIMES=1, meaning
that
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #9 from the_ma...@seznam.cz 2010-08-14 16:18 CST ---
(In reply to comment #8)
> Yes, I was mixed up. A Linux destination should have no trouble hard-linking
> symlinks.
>
> New theory: the receiving rsync was configured wit
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #10 from m...@mattmccutchen.net 2010-08-14 16:32 CST ---
(In reply to comment #9)
> in this case, why problem occurs only
> when rsync server is hpux? I would expect the same behaviour with Linux rsync
> servers too. But no,
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #11 from the_ma...@seznam.cz 2010-08-14 16:42 CST ---
Ok, when -i added as rsync parameter.
r...@zaloha pokus]# grep .tsm rsync3.traced
[pid 9438] lstat("home/zumrova/.tsm", 0x7fffba96ea10) = -1 ENOENT (No such
file or dire
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #12 from the_ma...@seznam.cz 2010-08-14 16:46 CST ---
And straces when without -i:
First run:
r...@zaloha pokus]# grep .tsm rsync1.traced
[pid 9169] lstat("home/zumrova/.tsm", 0x7fff2ff0e040) = -1 ENOENT (No such
file or d
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #13 from the_ma...@seznam.cz 2010-08-14 16:52 CST ---
Sorry, mistake:
Second run with --lin-dest
[r...@zaloha pokus]# grep .tsm rsync2.traced
[pid 9473] lstat("home/zumrova/.tsm", 0x7fffd42da910) = -1 ENOENT (No such
file o
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #14 from the_ma...@seznam.cz 2010-08-14 17:20 CST ---
I created .tsm on one one Linux rsync servers, rsynced, moved and rsynced with
--link-dest:
[r...@zaloha pokus]# grep .tsm rsync2_samba.traced
[pid 9576] lstat("home/zum
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #15 from the_ma...@seznam.cz 2010-08-14 17:26 CST ---
Eh, too late night for me. Once again, the same sutuation but againts one of
linux servers:
[r...@zaloha pokus]# grep .tsm rsync2_samba.traced
[pid 9587] lstat("home/zum
On 09/08/10 09:32, Matt McCutchen wrote:
> On Sat, 2010-08-07 at 19:54 +1200, Morgan Read wrote:
>> I've been running this command, with the accompanying error:
>> [r...@mythtv ~]# ssh -t rs...@192.168.1.40 sudo rsync -avzAXH
>> --delete-after -e /home/rsync/bin/rsync_ssh /home/
>
>> building file
https://bugzilla.samba.org/show_bug.cgi?id=7618
--- Comment #16 from m...@mattmccutchen.net 2010-08-14 23:26 CST ---
I just noticed the "no symtimes" (i.e., HAVE_LUTIMES off) in the "rsync
--version" output for the client in comment #0. Consistent with that, rsync
does not attempt to
https://bugzilla.samba.org/show_bug.cgi?id=7621
Summary: Special handling of lutimes ENOSYS failures does not
work as intended
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
Seve
On Wed, 2010-08-11 at 10:18 -0700, travis+ml-rs...@subspacefield.org
wrote:
> I often push files from my user account over SSH to my web server, and
> want them owned by www-user, which may not have a login shell, should
> never accept remote logins, and who may not have a ~/.ssh directory
> (and i
23 matches
Mail list logo
