Messages in this thread | | | From | Ingo Oeser <> | Subject | Re: Never mind. Re: Signal left blocked after signal handler. | Date | Thu, 27 Nov 2003 10:11:51 +0100 |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 26 November 2003 22:53, Albert Cahalan wrote: [2.4 vs. 2.6 wrt. thread synchronous signals] > How about making the process sleep in a killable state? > > This is as if the blocking was obeyed, but doesn't > burn CPU time. Only a debugger should be able to > tell the difference.
This has 2 problems:
1) Servers and PID files or servers and simple monitoring software. 2) Processes spawned from init, which will not respawn.
Regards
Ingo Oeser
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/xb/mU56oYWuOrkARAmNaAKCL1uojbOpMtMdSvAl6B9rBW51CTgCgypP8 NlbaIac25oefxcHL9WlzxyE= =h6UI -----END PGP SIGNATURE-----
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |