Nagios killing xmessage

[Hugo van der Kooij]

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

Redder,Greg wrote:
> Andreas,
> 
> Thank you for the response.  Unfortunately backgrounding was the first thing I tried.  The pid is still owened by nagios and thus I thought that a nohup would work since the parent pid becomes 1.  No luck Nagios still seems to kill it.  I thought nohup would be the trick :-(

Let us go back to the drawing board. I would think more along the lines of:
 - Nagios alert messages add or remove messages from a text file. (Say 1
 event per line).
 - xmessages checks the file each minute or so and if it is not empty it
will show the content. Perhaps just restart xmessage with the new
content if the content has changed.

It is a rather crude scetch but it might point you into a direction you
may not have considered yet.

Have you considered looking at that firefox plugin? It will propably do
something quite similar to what you want to achive.

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.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHMRZRBvzDRVjxmYERAqzfAJ9ueJWG0l53mJ6K86Yy8j2NQaoTQACggm0T
SVnsTLCFA0+PiKcKytRmc48=
=cIYP
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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