What comes after suspend blockers

Posted Jun 3, 2010 10:24 UTC (Thu) by nix (subscriber, #2304)
Parent article: What comes after suspend blockers

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.

What comes after suspend blockers

Posted Jun 3, 2010 18:54 UTC (Thu) by dmk (guest, #50141) [Link] (2 responses)

>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

Posted Jun 14, 2010 13:28 UTC (Mon) by oak (guest, #2786) [Link] (1 responses)

Before KILL one could try SIGXCPU...

What comes after suspend blockers

Posted Jun 14, 2010 20:24 UTC (Mon) by aigarius (subscriber, #7329) [Link]

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