rsync - Oct 2001 - @ERROR: chroot failed

Why would I be getting this on a box? I have the same permissions on
many other directories. Using verbose mode shows nothing more then the
error in the Subject line.

Any help is appreciated.
-- 
Jason G Helfman                                                                 
Network Administrator                                                           
BizRate.com
310.754.1264 desk
310.466.2319 cell

	Fingerprint: DA13 C109 072B CC12 B568  8D84 E9A2 6A7D C479 BCFB
            GnuPG http://www.gnupg.org  Get Private!  1024D/D75E0A36

Three things:
   Does the system support chroot?
   Is the rsyncd running as root?
   Is the path correctly specified in the rsyncd.conf?
I can't think of anything else I've run into or read of, to cause that
problem.
If it's not number three, try running it as root.  If that fails, try adding
use chroot = no
to your rsyncd.conf.

Tim Conway
tim.conway@philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips
Available as n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me.... Tim?"





Jason Helfman <jhelfman@bizrate.com>@lists.samba.org on 10/10/2001
12:47:11 PM

Sent by:  rsync-admin@lists.samba.org


To:     rsync@lists.samba.org
cc:      (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:  @ERROR: chroot failed
Classification:



Why would I be getting this on a box? I have the same permissions on
many other directories. Using verbose mode shows nothing more then the
error in the Subject line.

Any help is appreciated.
--
Jason G Helfman
Network Administrator
BizRate.com
310.754.1264 desk
310.466.2319 cell

     Fingerprint: DA13 C109 072B CC12 B568  8D84 E9A2 6A7D C479 BCFB
            GnuPG http://www.gnupg.org  Get Private!  1024D/D75E0A36

On Wed, Oct 10, 2001 at 11:47:11AM -0700, Jason Helfman
wrote:
> Why would I be getting this on a box? I have the same permissions on
> many other directories. Using verbose mode shows nothing more then the
> error in the Subject line.
That error is coming from an rsync daemon server.  Are you administering
that side?  If so, what does the rsyncd.conf look like?  Most likely it is
either
    a) it's run as root but there's no "uid = root"
    b) it's not run as root and there's no "use chroot = no"

- Dave Dykstra