On Tue, May 02, 2006 at 09:13:47AM -0400, Gary Aviv wrote:
> In fact, even if the link is invalid it should be transfered.
The desire is to make a daemon that is running without chroot work as
closely as possible to a daemon that is running with chroot. So, what
we definitely need to avoid is let
On Mon, 1 May 2006, Wayne Davison wrote:
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 j
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 sanit
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/ia
