On Wed, Feb 07, 2001 at 05:42:55PM -0500, Diab Jerius wrote:
> Here's a mystery (to me at least!):
>
> I've got a symbolic link on the source disk which looks like this:
>
> > ls -l /proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp
> [...]
> /proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp ->
> /proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp-D20000304
>
>
> my rsyncd.conf looks like:
>
> [proj_axaf_simul_bin_xfer]
> path = /proj/axaf/Simul/bin
> read only = no
>
>
> I run rsync on the source machine as
>
> rsync -vrlptx --port=9753 \
> --delete \
> --force \
> --include '*/' \
> --include '**mips*-IRIX*/*' \
> --exclude '*' \
> /proj/axaf/Simul/bin/ jeeves::proj_axaf_simul_bin_xfer
>
>
> and it turns the file on the remote disk into:
>
> jeeves-155: ls -l /proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp
> [...]
> /proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp ->
> proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp-D20000304
>
> Whatever happened to the leading /?
>
> Thanks,
> Diab
>
>
Are you using "use chroot = no" in your rsyncd.conf? From the rsynd.conf
man page under "use chroot":
For writing when "use chroot" is false, for security reasons
symlinks may only be relative paths pointing to other files
within the root path, and leading slashes are removed from
absolute paths.
- Dave Dykstra
