In this particular instance, after digging around
a bit, it seems the receiving host was totally over
taxed with no available memory or sockets to
spare.
I'm sure that's the source of my issues as I've
switched from ssh to remsh with the same outcome.
I would say at this point it's definitely not an issue
with rsync.
Cheers!
-b
-->-----Original Message-----
-->From: Dave Dykstra [mailto:[EMAIL PROTECTED]]
-->Sent: Monday, June 26, 2000 10:15 AM
-->To: Williams, William
-->Cc: Multiple recipients of list RSYNC
-->Subject: Re: Hanging with HP? (2.3.2 and ssh 1.2.26)
-->
-->
-->On Fri, Jun 23, 2000 at 01:10:06PM +1000, Williams, William wrote:
-->> Sorry, got my fingers crossed on the send button.
-->>
-->> Anyone seen rsync 2.3.2 hang with ssh 1.2.26 on
-->> HP 10.20?
-->>
-->> I have some issues that I can't pinpoint and without
-->> truss, I really can't tell what the heck's going on.
-->>
-->> Any help would be appreciated.
-->>
-->> PS> I searched the threads for an HP specific
-->> one regarding hanging and didn't see anything.
-->>
-->
-->I don't believe anyone has reported that, although it is
-->known that the
-->workaround in rsync 2.3.2 is not fool-proof for preventing ssh hangs.
-->
-->In my experiences with HPUX 10.20 and rsync in the --daemon mode, I
-->reguarly see networking errors and ignore them and since I
-->try every hour
-->from cron they eventually recover. I use --timeout 120 so
-->things don't
-->hang forever.
-->
-->- Dave Dykstra
-->
