In message , Martin Gregorie
 writes
>It would be interesting to know what happened between  10:52:56 and
>12:36:52 - assuming that the clocks on the two systems are synchronised.
>

So far as I can tell, the clocks are synced (they are certainly within a
second).

Top and ps on the source machine suggests the ssh and rsync processes
have terminated, and on the target, the ssh and rsync processes exist,
but don't appear to be doing anything.

>I wonder if a wireshark journal would show anything useful. If the link
>normally falls over as soon after it seems to have this time AND you
>filter the stream to show just packets sent and received by the source
>system, there shouldn't be too many unrelated packets to bypass.
>

When it works, it takes 70-80 seconds start to finish, when it doesn't
it is 16-17 minutes before the target processes terminate.  The first
few seconds see the normal rsync stuff in the log, then nothing.

There shouldn't be any packets from source to target for about 90
minutes after this job, but there will be other traffic on the network,
some of it to the target (but from other sources) and in general.

>Wireshark would be my tool of choice after I'd looked at the logs on both
>ends of the link. These days it has a decent graphical interface. Anybody
>who knows enough about networks to set up a hardwired LAN and configure
>their hosts to talk to each other should find Wireshark fairly easy to
>use.
>

Time permitting, I might have a play with that tomorrow, and see if I
can make sense of it.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

--- SoupGate-Win32 v1.05