Henry F. Camacho Jr a écrit : > Matt: > > Hmmm... Matt, this is exactly what init is designed to do, it will > respawn any daemon that stops running, and reruns it automatically. > Some people use something called daemon tools, or something called > supervisor, all which work just fine. I think init does a great job of > this also assuming the daemon is well behaved. >
init wasn't designed for that. I learned this the hard way. init is ok for system services that were tested for long and are simple enough (they may theoritically crash, but this almost never happens, and if this ever happens, they are fixed soon). now, the same functionality can be implemented with one's own daemonizer/manager. you can use a periodic task to check spamd and restart it. or you could hack the code to add a super-parent that waits for signals and restarts the "parent" (its child) if bad things happen. of course, if spamd crashes, then it would be good to know why/when that happens, so it can be fixed if possible.
