Hello,
I am trying to run rsync under my own userid on a high-numbered port.
The problem is that, when I use the --daemon option, I get an error
saying that a chroot() call failed.
My config file does *not* have any chroot call in it.
How can I avoid a chroot() invocation when running as a norma
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.
To: [EMAIL PROTECTED]
Subject: an unwanted chroot() call
From: Daniel Ortmann <[EMAIL PROTECTED
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 rsy
On Thu, Nov 13, 2003 at 09:51:51AM -0500, Joe Batt wrote:
> 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 (m
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
Lao Coon <[EMAIL PROTECTED]> writes:
> 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 ma
