[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multiple pids
From: |
Jan-Henrik Haukeland |
Subject: |
Re: multiple pids |
Date: |
Wed, 19 Apr 2006 21:53:26 +0200 |
On 19. apr. 2006, at 20.26, Marc Petitmermet wrote:
Usually one of those processes are the control-process and you
only need to monitor, start and stop that one. It's probably the
one with the lowest pid of the eights. Test by sending this
process the SIGTERM signal to check if it takes down the rest.
Not for nfsd. As I mentioned before these are 8 independent
daemons; there is no parent or control process.
Well, monit cannot handle a multiple pids file as you found out. You
need to either write 8 'check process' tests or much easier, monitor
the port number used by nfs. For instance using something like this:
check host some.host.name with address localhost
start = ".."
stop = ".."
if failed port 2049 then ...
--
Jan-Henrik Haukeland
- multiple pids, Marc Petitmermet, 2006/04/19
- Re: multiple pids, Jan-Henrik Haukeland, 2006/04/19
- Re: multiple pids, Marc Petitmermet, 2006/04/19
- Re: multiple pids,
Jan-Henrik Haukeland <=
- Re: multiple pids, Marc Petitmermet, 2006/04/19
- Re: multiple pids, Jan-Henrik Haukeland, 2006/04/20
- Re: multiple pids, Marc Petitmermet, 2006/04/20
- Re: multiple pids, Jan-Henrik Haukeland, 2006/04/20
- Re: multiple pids, Paul Monaghan, 2006/04/20
- Re: multiple pids, Martin Pala, 2006/04/20
- Calling an external program from monit [was: Re: multiple pids], Jan-Henrik Haukeland, 2006/04/20
- Re: Calling an external program from monit [was: Re: multiple pids], Marc Petitmermet, 2006/04/20