[Klug-general] SSH and Rsync weirdness

[Karl Buckland]

In the past I've used kill directly with a process ID, or 'killall rsync'.

Like Laurence, I would assume that any forked processes should also be
killed (and my experience backs this up). Could you see which processes
were actually creating traffic? My first guess would be to assume that
something else was using the traffic instead of your killed process.

Karl



On 14 March 2013 12:25, Laurence Southon <laurence at southon.uk.net> wrote:

> On 14/03/13 11:58, Paul Littlefield wrote:
> > If I kill a rsync-over-ssh process, should that stop the data transfer
> > right then?
> >
> > I would have thought so.
> >
> > I only ask because it appears that the 'transfer' was still continuing
> > hours later and clogging up my customer's broadband.
> >
> > I checked this with 'iftop' and 'ntop', and in the end it just
> > stopped... 4 hours later than it should have done.
>
> Guessing, but it's normal for rsync to fork a number of processes when
> started.
>
> In theory pkill should kill them all, but perhaps rsync needs a SIGKILL
> rather than the default SIGTERM to be certain.
>
> Regards,
>
> LS
> --
> Laurence Southon
> Tiger Computing, Bexley
> www.tiger-computing.co.uk
>
> _______________________________________________
> Kent mailing list
> Kent at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/kent
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/kent/attachments/20130314/f96f0b4e/attachment.html>