Antwort: Re: NSCA and long output

[Thomas Guyot-Sionnest]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28/05/08 01:12 AM, Thomas Borger wrote:
>> Looking at the NSCA sources, common.h has:
>> #define MAX_PLUGINOUTPUT_LENGTH       512
>> I'm guessing that's the issue right there.  The first thing I'd try is
>> to bump that up to 4096, and recompile send_nsca and nsca.  I haven't
>> looked very carefully at the source or tried this myself, but it seems
>> like a good place to start.
>> Mike
> 
> Yes that's right. I use this since a couple of days. But you have to
> check the value in nagios source code (include/nagios.h) too.
> It muste be at least the same or higher.

A value of 4096 will likely work well in Linux as pipes guarantee that
this many bytes can be written at once in that OS. POSIX requires 512
bytes so this may vary between operating systems (PIPE_BUF should tell
you what the limit is).

Anything larger will likely cause fragments to be lost and/or
interleaved (the latter can happen if you have multiple writers at the
same time). See pipe(7) for more details.

The proper fix would bu using PROCESS_FILE instead to load long output.

Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIPg436dZ+Kt5BchYRAjWNAKDmDsCnTFCAoiuapdy/KKShPyaA0wCffry8
H4pbn7Iv+aqaj1Lp+kIrJjs=
=cEsA
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at 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