Open calestyo opened 6 months ago
btw: It's clear that one cannot catch SIGSTOP
, but if the problem itself (i.e. that the fails after SIGCONT
would be unfixable, then maybe one could do something to at least prevent from accidental SIGSTOP
, which may happen as easy as doing a Ctrl-Z
in the terminal... I thought about temporarily disabling the stop CHAR
, like via stty susp ''
.
Hey.
From [0]:
I have experienced this myself already some years ago and apparently others[1], too.
When stopping a
send|receive
pipeline (both on the same host, i.e. nossh
or so involved), and continuing it again, the whole thing dies immediately with an:Which is particularly annoying when one wanted to make a backup of 9TB and was nearly finished and had forgotten that this breaks. ;-)
Any way to have that fixed?
Cheers, Chris.
PS: kernel 6.5.10