On Wed, 2006-03-08 at 00:49 +0100, Marc Dirix wrote: > Like I said, a daemon should run indepedentally from the shell > implemantation.
But you haven't said _why_. > And secondly, starting from inittab is IMHO only usefull for daemons > which tend to get killed or die, and therefor is a quickfix for not propperly > working daemons. You've already said this, but you haven't said _why_. > Furthermore, a standard init only tries X time to restart a program, > afterwards it stops anyways. Standard init doesn't do this. Standard init will back off after so many failed stops, but this is an effort to reduce CPU time. If the program dies 5 times in a second, a few minutes are delayed. If the program dies 5 times in a day, there's no delay. Furthermore, an init.d script won't get restarted EVER. > And a good working init.d script doesn't stop my computer from booting > when the daemon fails to start. It does give me a warning right away. It's the not-working init.d scripts or daemons that stop the computer from booting. But even working init.d scripts and working daemons can be killed or stopped for lots of reasons, and unless you duplicate the work of init, or manually intervene, they won't start back up. -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/
