LWN: Comments on "What comes after suspend blockers"

What comes after suspend blockers

aigarius — Mon, 14 Jun 2010 20:24:53 +0000

Yep, as one of "... series of increasingly urgent signals ..." before SIGKILL, just as mentioned in that text.

What comes after suspend blockers

oak — Mon, 14 Jun 2010 13:28:52 +0000

Before KILL one could try SIGXCPU...

What comes after suspend blockers

dmk — Thu, 03 Jun 2010 18:54:34 +0000

>SIGSTOP, surely? Just as uncatchable, and we're trying to stop them chewing CPU, not kill them stone dead.

Well no. Peter actually meant to kill them.

What comes after suspend blockers

nix — Thu, 03 Jun 2010 10:24:59 +0000

Another is to have a user-space daemon which informs processes that it's time to stop what they are doing and go idle. Any process which fails to comply can be reminded with a series of increasingly urgent signals, culminating in SIGKILL if need be.

SIGSTOP, surely? Just as uncatchable, and we're trying to stop them chewing CPU, not kill them stone dead.