<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.73"> <TITLE>AW: [Nagios-users] output more than 80 characters</TITLE> </HEAD> <BODY> hi basile, when i'm right, you have to change MAX_INPUT_BUFFER in common/common.h too. regards, chris -----Ursprüngliche Nachricht----- Von: nagios-users-admin@lists.sourceforge.net [<A HREF="mailto:nagios-users-admin@lists.sourceforge.net">mailto:nagios-users-admin@lists.sourceforge.net</A>]Im Auftrag von Basile Mathieu Gesendet: Freitag, 23. Jänner 2004 13:30 An: nagios-users@lists.sourceforge.net Cc: pla@softflare.com; ejl@man.fwltech.com Betreff: RE: [Nagios-users] output more than 80 characters i m doing my own plugins it s to make snmp management i find in the source code the constant MAX_PLUGINOUTPUT_LENGTH and change it to 1000 but it doesn t work it seems to be a bit more difficult :) A 11:32 23/01/2004 +0000, vous avez écrit : >Does it output the extra characters on the command line when you run >./check_http or whichever plugin you are testing? If so, maybe there is a >maximum limit of 80 characters in the nagios web pages too. > >Ewan > > > -----Original Message----- > > From: Basile Mathieu [<A HREF="mailto:Basile.Mathieu@siris.sorbonne.fr">mailto:Basile.Mathieu@siris.sorbonne.fr</A>] > > Sent: 23 January 2004 11:06 > > To: nagios-users@lists.sourceforge.net > > Subject: [Nagios-users] output more than 80 characters > > > > > > i post a mail yesterday because i want to change the 80 > > characters of the > > output of plugins > > i think i find it and i recompile nagios but it doesn t work > > if someone know where it is defined > > it will help me > > thanks > > basile > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > <A HREF="http://www.eclipsecon.org/osdn" TARGET="_blank">http://www.eclipsecon.org/osdn</A> > > _______________________________________________ > > Nagios-users mailing list > > Nagios-users@lists.sourceforge.net > > <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users" TARGET="_blank">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 > > > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. ><A HREF="http://www.eclipsecon.org/osdn" TARGET="_blank">http://www.eclipsecon.org/osdn</A> >_______________________________________________ >Nagios-users mailing list >Nagios-users@lists.sourceforge.net ><A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users" TARGET="_blank">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 ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. <A HREF="http://www.eclipsecon.org/osdn" TARGET="_blank">http://www.eclipsecon.org/osdn</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users" TARGET="_blank">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 </BODY> </HTML>