Dave Dykstra wrote:
>
> On Wed, Oct 25, 2000 at 04:47:27PM +0200, Eckebrecht von Pappenheim wrote:
> > Dave Dykstra wrote:
> >
> > > Were using rsh, ssh, or daemon mode?
> >
> > I used ssh 1.2.27 on both machines. Again, with 2.3.1 we didn't have any
> > hangs at all...
> >
> > Eckebrecht
>
> Has it been compiled without the USE_PIPES in configure? That's been
> recently re-confirmed to be necessary to work with rsync 2.4.x.
>
I'll tell you tho whole stroy now :-)
We started with rsync 2.3.1 on a solaris 2.5.1 and 2.6 compiled with
./configure --prefix=/opt/local/rsync; make; make install
to sync our internal webserver with the public webserver. Then we added
4 Linux-Boxes with RedHat 6.2 and used the rsync 2.4.0 which comes with
RedHat (I don't know, how they compiled it). Worked without any
problems. We do automated rsyncs betwenn all of this machines several
times a day, no problems. The connection in our Cluster use rsh, betwen
the Cluster and the internal network with ssh (1.2.27 on solaris,
OpenSSH 2.1.1 on Linux)
Then I downloaded 2.4.6 and developed my '--time-only'-patch on it and
compiled and installed on all machines with
./configure --prefix=/opt/local/rsync-2.4.6; make; make install
Next morning I found a dozen or more rsyncs hanging. I can't tell, if
they all used ssh, sorry.
Now I installed 2.3.1 on all machines with my '--time-only'-patch added:
./configure --prefix=/opt/local/rsync-2.3.1; make; make install
and everthing works fine... It looks as if the hang-problem was
introduced with 2.4.x where x > 0.
Back to your question: How can I tell, if it's compiled with USE_PIPES?
I grepped for this in the source directories of 2.3.1 and 2.4.6 and
can't find any occurances .
Eckebrecht
--
------------------------------------------------------------------------
Eckebrecht von Pappenheim, network administration
Verlag Heinz Heise GmbH & Co KG, Helstorferstr. 7, D-30625 Hannover, FRG
EMail: [EMAIL PROTECTED] - Tel: +49 511 5352 242 - FAX: +49 511 5352 479
http://www.heise.de/
