It's just a feeder script, so in the end my solution was just to issue init.d/mydaemon start through cron on an hourly basis. It's not vital that it run ALL the time just most of the time, and the daemon will already refuse to let more than 1 run at time.
I know it seems like a kludge, but adding any extra overhead would strain an aready resource constrained environment. Thanks for the tips though. They'll probably come in handy in the future, so I'm bookmarking this thread :) On Sat, Dec 7, 2013 at 5:26 PM, Gabriel Gunderson <[email protected]> wrote: > On Sat, Dec 7, 2013 at 4:07 PM, Joshua Elliott <[email protected]> wrote: > > I've used monit <http://mmonit.com/monit/> for something like this > before. > > It can restart the daemon when it crashes, or when it uses too much > > memory/cpu. > > I've also used this with good results. > > > Gabe > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
