obsess_over_service

[Andreas Ericsson]

Gabriel Constantinescu wrote:
> It seems that there is a problem with the init script. It does not stop 
> the application properly, there are still nagios instances running after 
> issuing the stop command several times. That was the problem why nagios 
> did not take into consideration my configuration changes because it did 
> not restart or reload.
> Is that a bug?

Sort of. It's the worker threads that reap checks and such that have to 
wait for forked children before exiting. It's graceful, see.

> I noticed the same problem in version 1.2. The only 
> workaround is to kill -9 all nagios instances...
> 

Not the same problem at all. That was a bug in the init-script. This is 
a missing feature in nagios code (nagios doesn't force-kill forked 
instances when it catches sigterm).

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null