an unwanted chroot() call

[Joe Batt]

Would it help if rsync detected whether it is run as root or not and
enable or disabled these features automatically (with warnings).  I've
wasted lots of time trying to get rsync to work in userland due to
safety checks like this (my case was --link-dest assuming -ugp), though
I understand why rsync defaults to very safe use for root.  Maybe more
warnings to stderr would help.

Joe

On Thu, 2003-11-13 at 09:15, Lao Coon wrote:
> Daniel Ortmann wrote:
> 
> >Ok, I figured out the answer, and as a result I have a suggestion:
> >
> >The rsyncd.conf documentation for "use chroot" should specify that:
> >
> >    "use chroot = yes" is the default.
> >
> >  
> >
> Oh, but it does. Quote from man rsyncd.conf
> 
>        use chroot
>               If  "use  chroot"  is  true, the rsync server will chroot 
> to the
>               "path" before starting the file transfer with the 
> client.   This
>               has the advantage of extra protection against possible 
> implemen-
>               tation security holes, but it has the disadvantages of 
> requiring
>               super-user  privileges,  of  not  being  able to follow 
> symbolic
>               links outside of the new root path when reading, and of 
> implying
>               the  --numeric-ids option because /etc/passwd becomes 
> inaccessi-
>               ble.  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.
>               The default for "use chroot" is true.