Alex de Kruijff
freebsd at akruijff.dds.nl
Mon Nov 24 09:46:17 PST 2003
On Mon, Nov 24, 2003 at 09:02:29AM +0300, Sergey 'DoubleF' Zaharchenko wrote:
> On Mon, 24 Nov 2003 02:11:39 +0100 Alex de Kruijff <freebsd at akruijff.dds.nl> probably wrote:
> > Dear Will,
> > I've moved you text to the buttom so its more readable for other.
> > On Sun, Nov 23, 2003 at 04:46:09PM -0800, Will Prater wrote:
> > > On Nov 23, 2003, at 1:57 PM, Alex de Kruijff wrote:
> > > >On Sun, Nov 23, 2003 at 10:52:48AM -0800, Will Prater wrote:
> > > >>List,
> > > >>
> > > >>What are most of you using to monitor the running daemons? I have been
> > > >>loooking into DJB daemontools which seems appropriate, but are there
> > > >>any others that you reccomend?
> > > >>
> > > >>If DJB's daemontools is the one, could I get some more examples? I am
> > > >>primarily trying to keep my mail system online: postfix, cyrus,
> > > >>saslauthd, mysql, and spamassassin.
> > > >
> > > >I would advise Nagios.
> > >
> > > Sorry, I mispoke. I will be using Nagios to monitor, but I need to make
> > > sure they will restart if there is an error. Will nagios do this as
> > > well?
> > >
> > I don't *think* so.
> > You could write a sh script (or any other) that does this. It could
> > contain this line:
> > result=px aux | grep SomeDaemon | wc -l
> > If the result is zero than SomeDaemon is not running.
> You'd be better off using "ps auxc" here (that is, print only argv):
> $ ps aux|grep aux
> df 642 0,0 0,4 648 444 p1 R+ 8:49 0:00,00 grep aux (sh)
> df 641 0,0 0,3 516 392 p1 R+ 8:49 0:00,00 ps aux
> <which is obviously wrong for your situation, since the "aux"
> `daemon' is not running>
> $ ps auxc|grep auxc
> <nothing, which is right>
Your ride i forgot that one. I'll give an adjustment:
result=px aux | grep SomeDaemon | grep -v aux | wc -l
Articles based on solutions that I use:
More information about the freebsd-questions