I've just installed Nagios 3 and begun to configure it for my network (25ish servers, all but 2 running Linux, 250ish workstations, all but about 25 running Ubuntu), and after slogging through "SSL error" on check_nrpe -- which means about 3 different things having nothing to do with SSL -- and the ever popular "audio embeds *aren't* application/wav; they're audio/x-wav, just ask my mime.types file" problems, I'm now up to the possibly uncommon way I want to use check_users...
I'm setting check_users (via nrpe) to warn at 1 and CRIT at 3 users -- I'm putting this on servers that, typically, have no humans logged in at all. Since that's true, I'd like to have the list of users from who -q returned as part of the status message. a) Is this a not uncommon usage, and when I patch the program, should I therefore post and or submit a patch to do this? b) How long can that status message become without breaking 1) nagios and 2) nrpe? Anyone have opinions, answers, or pointers? Cheers, -- jra -- Jay R. Ashworth Baylink [EMAIL PROTECTED] Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com '87 e24 St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274 Those who cast the vote decide nothing. Those who count the vote decide everything. -- (Joseph Stalin) ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Nagios-users mailing list Nagios-users@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