Package: debmirror
Version: 1:2.25
Severity: normal
Hi,
If I decide to cancel a debmirror run with CTRL+C, I often end up with
rsync processes continuing to download in the background:
Attempting to get lock ...
Updating remote trace files (using rsync) ...
receiving incremental file list
./
^C
$
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504)
[receiver=3.1.1]rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(632) [generator=3.1.1]
Warning: failed to use rsync to download extra files.
Getting meta files ...
rsync: [receiver] write error: Broken pipe (32)
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(1633)
[sender=3.1.1]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632)
[Receiver=3.1.1]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632)
[Receiver=3.1.1]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632)
[Receiver=3.1.1]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632)
[Receiver=3.1.1]
Killed
receiving incremental file list
dists/jessie-backports/
dists/jessie-backports/Release
164,420 100% 220.86kB/s 0:00:00 (xfr#1, to-chk=0/4)
receiving incremental file list
dists/jessie-backports/InRelease
Killed
Killed
Ignoring failed Release files.
I always end up having to do some kind of "killall -9 debmirror" and
"killall -9 rsync" dance to fix this.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
