I am running latest rsync version 2.6.8 on both ends. The receiver is a daemon. When I transfer a symbolic link like this: /tmp/rsync -av /opt/iat/IaT3.1.1/bin/* uxgary::root/opt/iat/IaT3.1/bin building file list ... done compile_plan.py -> ../python/compile_plan.py iat_status -> ../python/iat_status.py load_iat_xml.py -> ../python/load_iat_xml.py show_engine.py -> ../python/show_engine.py start_server.py -> ../python/start_server.py stop_server.py -> ../python/stop_server.py However, at the destination the .. is missing. for example the link "../python/compile_plan.py" becomes "python/compile_plan.py" at the destination. Gary Aviv This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful. Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
On Sat, Apr 29, 2006 at 01:48:28PM -0400, Gary Aviv wrote:> However, at the destination the .. is missing. for example > the link "../python/compile_plan.py" becomes "python/compile_plan.py" > at the destination.Is your daemon running without chroot? I just did a test, and rsync's symlink sanitizing is getting rid of the leading "../", even when the destination would not be outside the top directory of the module. This erroneous behavior has been going on as far back as I checked (which was 2.5.7), so it would appear that most people have "use chroot = yes" enabled in their daemons. I'll check into fixing this. Thanks for the report, ..wayne..