On Tue, Jun 15, 2010 at 01:40:43PM -0500, Chris Adams wrote: > Once upon a time, Casey Dahlin <cdahlin@xxxxxxxxxx> said: > > I'd say fire and forget or something close for most sysv initscripts. If > > you want to do better you need a modern tool like systemd/upstart/etc. > > Trying to do it better in bash just makes for piles of ugly, and the > > weird failure modes and corner cases will usually end up being worse > > than the problem. > > A well-behaved daemon should be doing all the checking possible before > forking to go into the background. The init scripts do check the exit > code, so configuration errors, failure to bind to sockets, etc. should > be (and in most cases are) caught that way. > Oh if only they were all well-behaved :) Yes, reading and acting on the information the daemon itself hands to you is obviously a good thing. --CJD -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
