On Sun, Mar 03, 2002 at 07:26:14PM +0100, Thomas Quinot wrote:
> Le 2002-02-27, Dave Dykstra ?crivait :
>
> > That wouldn't be very friendly to have to do for every module listed in
> > rsyncd.conf.
>
> Yep, hence my report :)
>
> > It would be interesting to do for a test though just to make
>
Le 2002-02-27, Dave Dykstra écrivait :
> That wouldn't be very friendly to have to do for every module listed in
> rsyncd.conf.
Yep, hence my report :)
> It would be interesting to do for a test though just to make
> sure that this is really the problem. I'm surprised that no-one else would
>
On Wed, Feb 27, 2002 at 08:03:46AM -0700, Rusty Carruth wrote:
> Thomas Quinot <[EMAIL PROTECTED]> wrote:
> > When using rsync 2.5.2 as daemon on a Solaris 2.5.1 box, I cannot
> > copy data to rsync volumes with option 'use chroot'; I get the
> > following messages on the client:
> > pipe failed
Thomas Quinot <[EMAIL PROTECTED]> wrote:
> ...
> What seems to occur on the server is that socketpair(3)
> (not pipe(2)) is called, which needs to open /dev/ticotsord.
> Since I do not have a /dev in the chroot directory,
> this call fails.
Why not just make a /dev in the chroot and put only tioc
When using rsync 2.5.2 as daemon on a Solaris 2.5.1 box, I cannot
copy data to rsync volumes with option 'use chroot'; I get the
following messages on the client:
pipe failed in do_recv
rsync error: error in socket IO (code 10) at main.c(375)
rsync: connection unexpectedly closed (69 bytes r
