I've had a further look in to this bug and it doesn't actually appear to be an issue with the nagios2 init script. I think the problem is actually in the killproc() sub-routine that's part of /lib/lsb/init- functions (lsb-base).
killproc() from /lib/lsb/init-functions (lsb-base) does not check to see what type of signal was sent. If signal 1 is sent (HUP), it removes the PID file. The PID file shouldn't be removed on this action (I may be wrong?). I'll raise another bug against init-functions for lsb-base and see what feedback I get. Anyway, I've attached a patch for the original problem where the nagios2 init script has the wrong PID file, although this isn't a major problem. More for consistency. ** Attachment added: "Patch to correct PID file name for consitency." http://launchpadlibrarian.net/10934576/nagios2.init.patch -- nagios2 init script has wrong PID file and incorrectly removes PID file on a reload. https://bugs.launchpad.net/bugs/174466 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
