<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>[Nagios-users] Null mailer - no notifications for contacts that want to view CGIs only (maybe notif to an ML)</TITLE> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD> <BODY> <DIV dir=ltr align=left>I you do not need any form of notification at all for a user that can 'view' nagios, it is as simple as creating a user (by whatever authentication mean you use, I authenticate to active Directory in my environment) and then define in the cgi.cfg what the user can see. There is no need to create a contact for that user for them to view the cgi's.</DIV> <DIV dir=ltr align=left> </DIV> <BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: Stanley Hopcroft [mailto:Stanley.Hopcroft@IPAustralia.Gov.AU] Sent: Sunday, June 13, 2004 7:46 PM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Null mailer - no notifications for contacts that want to view CGIs only (maybe notif to an ML) </DIV> <DIV></DIV> Dear Ladies and Gentlemen, Does anyone else have a situation where contacts (ie those who want to view the Nag CGIs) do _not_ want individual notifications - perhaps because one of the other contacts is a non personal contact that corresponds to a mailing list and those responsible for the host/service read this mailing list ? Alternatively, a site may require that instead of personal notification, all host and service faults are entered into a 'request tracking' or 'service desk' system but authenticated access to the CGIs is still required for the host/service administrators. I have dealt with this by defining a null notification command ('test 1 -eq 1' but maybe the Bourne shell ':' ['A null command that returns a 0 (true) exit value.'] is better) but Nag must still fork a shell to run this. Is a better way simply to - not define notification commands - leave them out - in the contact template - individually define notification commands for each contact that requires notification ? If that is the case, some of the benefit of the contacts template is lost since most contacts will require notification. OTOH it seems quite sensible and feasable to do this. Is it possible to define a notification command that does _not_ oblige Nagios to fork /bin/sh ? What do others do about this ? Is there any interest in hacking the 1.x notification code to simply skip further processing ('No-op, no-op the angel did say) for a token representing a 'null mailer' ? Perhaps a better way of dealing with this and other related problems is by having more than one level of inheritance from templates - many templates can be constructed that inherit attributes from any parent template and its parents. This may in fact be how it is done in Nag 2.x. Yours sincerely. -- ------------------------------------------------------------------------ Stanley Hopcroft ------------------------------------------------------------------------ '...No man is an island, entire of itself; every man is a piece of the continent, a part of the main. If a clod be washed away by the sea, Europe is the less, as well as if a promontory were, as well as if a manor of thy friend's or of thine own were. Any man's death diminishes me, because I am involved in mankind; and therefore never send to know for whom the bell tolls; it tolls for thee...' from Meditation 17, J Donne. ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! <A href="http://www.installshield.com/Dev2Dev/0504">http://www.installshield.com/Dev2Dev/0504</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </BLOCKQUOTE></BODY></HTML>