|
|
|
|
|
|
by T3OU-736
1913 days ago
|
|
|
Can't catch those signals, but under a very specific sets of circumstances, they could be... not quite ignored, but basically, that is behavior. Things which are pending completion of I/O won't die as soon as SIGTERM or SIGKILL are sent to them. If you have ever tried to kill a process which had open file handles on a stale NFS mount, you have experienced this behavior. Causing it to happen deliberately is a lot more challenging, as well as not having a process actually be BLOCKED due to I/O, but it was[1] doable. [1] haven't tried to do this in about a decade, so won't speak about the currency of this approach, but back then, with some clever assembly and a kernel module, it was doable. |
|
|