similar to: DO NOT REPLY [Bug 5457] New: Add a client-side --munge-symlinks option

https://bugzilla.samba.org/show_bug.cgi?id=4263 Summary: Symlinks gets corruped when rsyncd is used to 'put' the symlink. Product: rsync Version: 2.6.8 Platform: Sparc OS/Version: Solaris Status: NEW Severity: critical Priority: P3 Component: core AssignedTo:

Hello, I''ve been using puppet fairly successfully on a 10 server cluster, so I thought I had a decent idea of what I was doing. However, we''re starting a new project using a different virtualization system ( XenServer ), and I can''t seem to get puppet to accept my previous conf file. The error is a strange one to me: [root@centos6-exp2 ~]# puppet agent --test

CentOS 6.6 I've got two servers, server1 and hbs (honkin' big server). Both are running munge, and torque... *separately*. My problem is that I've got users who want to be able to submit from server1 to hbs. I see that munged can be pointed to an alternate keyfile... but is there any way to tell qsub what to use? (And yes, I got on the torque users' list, and I'm trying

There are two security advisories for people who run a writable rsync daemon. One affects only those with "use chroot = no" (which is not a very safe combination in general), and one affects a daemon that has daemon-excluded files that are being hidden in a module's hierarchy. Included are simple config-change suggestions that should help you to avoid the security issues. These

There are two security advisories for people who run a writable rsync daemon. One affects only those with "use chroot = no" (which is not a very safe combination in general), and one affects a daemon that has daemon-excluded files that are being hidden in a module's hierarchy. Included are simple config-change suggestions that should help you to avoid the security issues. These

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) -> "/rsyncd-munged/../init.d/inetd" What I am trying to do is

https://bugzilla.samba.org/show_bug.cgi?id=13364 --- Comment #3 from Chris Severance <samba.severach at spamgourmet.com> --- >enable munge-symlinks. That way the client will get back the same out-of-tree symlink as it started with This is a lousy option for backups. The only way to get my original links back is to pull the restore through rsync. Restoring directly from the rsyncd server

https://bugzilla.samba.org/show_bug.cgi?id=13364 Bug ID: 13364 Summary: rsyncd clips trims relative symlinks outside of source tree Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee:

Hello, i have found, that major distros (especially opensuse) ship their rsync packages with a lot of patches which i don`t find in the official rsync-patches git. Maybe there is a reason for that or i missed something or looked wrong, but for convenience/transparency i have compiled a list of those and ask if it would make sense to put them into the official rsync patches git, as most of them

https://bugzilla.samba.org/show_bug.cgi?id=7108 Summary: --fake-super should be nestable Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: matt at mattmccutchen.net

https://bugzilla.samba.org/show_bug.cgi?id=5789 Summary: rsync trying to set times on symlinks Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: paredes@aecom.yu.edu

https://bugzilla.samba.org/show_bug.cgi?id=5442 Summary: setting times to symlinks which do not point to existing files causes error reports Product: rsync Version: 3.0.3 Platform: All OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=4037 Summary: Rsync should obey --keep-dirlinks when searching basis dirs Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=6027 Summary: Error when rsync encounters empty symlinks Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Linux Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: kai@kaishome.de

On Mac OS X 10.5.2 I run rsync to keep a couple of instances of my / usr/local tree in sync. With Apple's rsync I run (e.g.): sudo /usr/bin/rsync --rsync-path=/usr/bin/rsync -E --progress -avu -- delete --dry-run --exclude=TeXLive-working-copy/ --exclude=context- update/ --exclude=.Spotlight-V100/ --exclude=.fseventsd/ \ -e "ssh -i /Users/gerben/.ssh/id_rsync -l root" \

https://bugzilla.samba.org/show_bug.cgi?id=5304 Summary: failed to set times (symlinks) Product: rsync Version: 3.0.0 Platform: All OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: gmoreno@wlu.ca QAContact:

https://bugzilla.samba.org/show_bug.cgi?id=6927 Summary: Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc. Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=7110 Summary: Symlink fake-super data is silently lost when sys_lsetxattr fails with EPERM Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at

https://bugzilla.samba.org/show_bug.cgi?id=6197 Summary: Perms/owner/group modifiers for "show" filters Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

How can I have both server-side and client-side symlinks? Server-side symlinks are needed for example when what appears to the user to be a single mounted directory is actually tens of little pieces tied together by symlinks. Having those symlinks coalesces many mounts that would all have to be perfect in parallel into a single mount that's either fully successful or not. Client-side