The following patch (adapted to rsync 2.5.5 from the one posted in
Dec. 2000, http://lists.samba.org/pipermail/rsync/2000-December/003349.html)
is necessary to prevent rsync from failing on creating FIFOs or UNIX
sockets on FreeBSD. Any chance for it to be integrated in a future
release of rsync?
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
>
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
Hi list,
Since upgrading rsync to version 2.5.2 on a Solaris 2.5.1 box,
I see plenty of
Warning: unexpected read size of 0 in map_ptr
when doing my nightly backup (rsyncing some directories
to an rsyncd on the same LAN). I have never seen this message
before, and I only see it on the Solaris ma
