With much hope I upgraded to rsync version 2.5.6 in hopes that it would
correct the symbolic link bug I have been wrestling with...
No dice. It still insists on dropping the leading slash from a symbolic
link outside the source tree. Interactively it still works fine, but as
a daemon it's busted.
See previous posting 'rsyncd treats symlinks differently' for details.
Can someone acknowledge this issue ? Is it a bug ? feature ? something
else entirely ?
Thanks
--
Karl A. Wieman voice: 212-409-3371
Director, Technology fax: 212-407-5697
BlackRock Financial Management Inc. e-mail: kwieman@blackrock.com
"Audacity is a virtue that should always be practiced with caution."
- Walter Slovotsky
On Wed, Jan 29, 2003 at 02:34:43PM -0500, Karl Wieman wrote:> With much hope I upgraded to rsync version 2.5.6 in hopes that it would > correct the symbolic link bug I have been wrestling with... > > No dice. It still insists on dropping the leading slash from a symbolic > link outside the source tree. Interactively it still works fine, but as > a daemon it's busted. > > See previous posting 'rsyncd treats symlinks differently' for details. > > Can someone acknowledge this issue ? Is it a bug ? feature ? something > else entirely ?Do you have use chroot = false set? If so, this is documented behavior. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt