Cannot copy symlinks: rsync: open(...) failed!!: No such file or directory (2)

2009-02-14 Thread Mi
Hi, I can't figure out how to backup a tree with symlinks. I either get errors like rsync: open(rc2.d/S20inetd) failed!!: No such file or directory (2) or (with --safe-link on the client and munge symlinks = yes on the server): ignoring unsafe symlink /etc/rc2.d/S20inetd (in backups) -

DO NOT REPLY [Bug 6106] --disable-debug does nothing

2009-02-14 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6106 way...@samba.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 6107] Need a way to ask configure to disable all use of iconv_open()

2009-02-14 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6107 way...@samba.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 6095] code 23 when files or directories disappear, instead of code 24.

2009-02-14 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6095 way...@samba.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 6043] rsync ignores -x for some file systems

2009-02-14 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6043 way...@samba.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: Should posters be required to join the list? (was: Bad habits)

2009-02-14 Thread Wayne Davison
On Wed, Jan 21, 2009 at 10:47:29PM -0500, Matt McCutchen wrote: I'm shifting my position on this issue because I've seen several problems that would be solved by requiring posters to join the list: I have decided that we'll try running the list that way and see how we like it: Non-member

TEST of the new list configuration

2009-02-14 Thread testbox
This is a test of the new list configuration as announced by Wayne today. This is only a test. Matt -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read:

Re: Macintosh rsync: Inconsistent Behaviour: Hints Appreciated

2009-02-14 Thread Warren Oates
On Fri, Feb 13, 2009 at 1:08 PM, Yves Petronin y.petro...@aliceadsl.fr wrote: I have also used Mike Bombich' very clear instructions foud at http://www.bombich.com/mactips/rsync.html in order to compile the folllowing version of rsync on OS10.4.11: rsync version 3.0.4 protocol version 30

Re: --link-dest=server::location/folder

2009-02-14 Thread Matt McCutchen
On Fri, 2009-02-13 at 04:24 -0700, lewis butler wrote: Hate to bug you again, but I went ahead and installed 3.0.5 and looked at --help and didn't see anything about incremental recursion. Incremental recursion is not mentioned in the --help output, but there's some information about it in

Re: uid/gid settings in rsyncd.conf not respected?

2009-02-14 Thread Matt McCutchen
On Thu, 2009-02-12 at 21:23 -0800, Harry Mangalam wrote: I've created a special user to backup a server which has some users who don't want all their files backed up, so I'm trying to address their concerns by using the uid= and gid= lines in rsyncd.conf to have the rsyncd run with

[SCM] rsync branch, master, updated. v3.0.3-151-g49c2407

2009-02-14 Thread rsync-cvs
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project rsync. The branch, master has been updated via 49c2407141e85d9e3ce2a507db4c2facb7cd74b5 (commit) via

[SCM] rsync branch, b3.0.x, updated. v3.0.5-15-g8fba76d

2009-02-14 Thread rsync-cvs
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project rsync. The branch, b3.0.x has been updated via 8fba76d5c323c3c4a4340f39b8000e6f4b22d0eb (commit) via

[SCM] rsync branch, master, updated. v3.0.3-152-gd39d60a

2009-02-14 Thread rsync-cvs
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project rsync. The branch, master has been updated via d39d60a129b82d0a2c99104538b2421de07dd67c (commit) from