One list please..
As noted in the source...
common/objects.h:#define MAX_PLUGINOUTPUT_LENGTH 352 /* max. length of plugin output */
This is due to the limation of max size of a non-interleaved write to a
pipe on linux.
-sg
On Wed, 7 May 2003, Roy Sigurd Karlsbakk wrote:
> hi
>
> When I try sending the following error (1) (clipped from the event log), it
> cuts it off, leaving only the this (2) left. The clipped text is then used in
> the notification.
>
> any chance of getting the full text?
>
> I've tried several times, and it looks like there's a low buffer somehow. How
> can I change this? I _need_ long logs.
>
> roy
>
>
> 1
> ----------------------------------------------------------------------------------------
> [25-04-2003 14:00:37] EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;display01;CP_FLYTOGET_LODALEN;1;Not ready yet.
> But might be. Don't know. Might be ok. Might be broken. Unable to tell. It's
> just Windows. Or unix. OS/2? I don't know. Total confusion. As if in a
> relation to Confuctus. I might be wrong, but is this a nagios error report?
> Possibly. But more likely, I'd say it's closer to a rather bored sysadmin
> write a long passive check text to nagios to see if Nagios has stopped
> chopping them off in mid sentence. Ok. That's all folks.
>
> 2
> ----------------------------------------------------------------------------------------
> Not ready yet. But might be. Don't know. Might be ok. Might be broken. Unable
> to tell. It's just Windows. Or unix. OS/2? I don't know. Total confusion. As
> if in a relation to Confuctus. I might be wrong, but is this a nagios error
> report? Possibly. But more likely, I'd say it's closer to a rather bored
> sysadmin write a long passive check text to na
>
>
--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]