From b99d73579511e7b85278edb65c540ca13f12aa3c Mon Sep 17 00:00:00 2001 From: Ton Voon Date: Mon, 24 Sep 2007 18:51:07 +0000 Subject: State that stderr should not have any output git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1796 f882894a-f735-0410-b71e-b25c423dba1c --- doc/developer-guidelines.sgml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'doc/developer-guidelines.sgml') diff --git a/doc/developer-guidelines.sgml b/doc/developer-guidelines.sgml index 7bfcc732..1ae419a2 100644 --- a/doc/developer-guidelines.sgml +++ b/doc/developer-guidelines.sgml @@ -87,11 +87,14 @@ the entire output to appear in a pager message, which will get chopped off after a certain length. + As Nagios does not capture stderr output, you should only output to + STDOUT and not print to STDERR. +
Print only one line of text Nagios will only grab the first line of text from STDOUT when it notifies contacts about potential problems. If you print - multiple lines, you're out of luck. Remember, keep it short and - to the point. + multiple lines, you're out of luck (though this will be a feature of + Nagios 3). Remember, keep your output short and to the point. Output should be in the format: @@ -139,8 +142,9 @@
Screen Output The plug-in should print the diagnostic and just the - synopsis part of the help message. A well written plugin would + usage part of the help message. A well written plugin would then have --help as a way to get the verbose help. + Code and output should try to respect the 80x25 size of a crt (remember when fixing stuff in the server room!)
-- cgit v1.2.3