sticky acknowledgements do not persist across nagios restarts in Nagios 3

[Hugo van der Kooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Paul wrote:
> Hello Nagios-Users,
> 
> I have nagios 3.0.4 in Solaris 10. When acknowledge a host that is down
> (with a sticky acknowledgement, and then restart the nagios daemon with a
> kill -HUP, it deletes the acknowledgement.

1: sticky acknowledgement

> This is not the correct behavior according to page 7 of the nagios-3.pdf
> document,
> 
>    "Acknowledgement comments that are marked as non-persistent are now
> only deleted when the acknowledgement is removed. They were previously
> automatically deleted when Nagios restarted, which was not ideal."

2: non-persistent acknowledgement

> Can anyone else verify this behavior?

In my view 1 and 2 are not the same thing.

Hugo.

- --
hvdkooij at vanderkooij.org               http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc

	A: Yes.
	>Q: Are you sure?
	>>A: Because it reverses the logical flow of conversation.
	>>>Q: Why is top posting frowned upon?

Bored? Click on http://spamornot.org/ and rate those images.

Nid wyf yn y swyddfa ar hyn o bryd. Anfonwch unrhyw waith i'w gyfieithu.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFJG8X+BvzDRVjxmYERAkUXAJ4u86BByhbqpVVkcxhqTG6LXtInEACfegp0
4I1+YbvzLkF+uLXv5z4/0zA=
=JMVp
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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