On Thu, Jul 10, 2014 at 8:39 AM, David G. Miller <dave at davenjudy.org> wrote: > >> Generally speaking, if a service is broken to the point that it needs >> something to automatically restart it I'd rather have it die >> gracefully and not do surprising things until someone fixes it. But >> then again, doesn't mysqld manage to accomplish that in a >> fully-compatible manner on Centos6? >> > Can't find the original post so replying and agreeing with Les. Have the > same ongoing problem with radvd. When My IPv6 tunnel provider burps, the > tunnel drops. The tunnel daemon usually reconnects but radvd stays down. > Solution: > > */12 * * * * /sbin/service radvd status > /dev/null 2>&1 || /sbin/service > radvd start 2>&1 > > in crontab. How hard is that? And without all of the systemd nonsense. Or, if you want things to respawn, the original init handled that very nicely via inittab. Also,running a shell as the parent of your daemon as a watchdog that can repair its environment and restart it if it exits doesn't have much overhead. Programs share the loaded executable code across all instances and you pretty much always have some shells running on a linux/unix box - a few more won't matter. -- Les Mikesell lesmikesell at gmail.com