On Tue, 2006-04-04 at 22:35 +0100, Roy Marples wrote: > As more and more init scripts "stopping" can trigger other services to > restart, it becomes very desirable for this not to happen. So I propose for > the next baselayout release (1.12.0_pre17) to default start-stop-daemon calls > to SIGINT for stop commands instead of the current SIGTERM. My testing on my > boxes has no adverse effects so far. > > So ...... thoughts? Good or bad idea? Reasons and explanations welcome :)
From a standards point of view, SIGINT is strictly meant to be an interupt from the keyboard, and SIGTERM is there to notify the process that it should stop. I'm uneasy about going against accepted, standardised, and decades-old UNIX behaviour at this level. Why are bind et al getting into the state that they do? If you attach a debugger to the running processes, what state are they in? Why does stopping dhcpd using SIGINT et al prevent that? What is dhcpd doing in its signal handler? That seems to be the real issue that needs investigating and fixing. I feel that changing the behaviour of start-stop-daemon is masking the symptom, rather than fixing the bug. Best regards, Stu -- Stuart Herbert [EMAIL PROTECTED] Gentoo Developer http://www.gentoo.org/ http://blog.stuartherbert.com/ GnuGP key id# F9AFC57C available from http://pgp.mit.edu Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C --
signature.asc
Description: This is a digitally signed message part
