Plugin Output

[Jason Marshall]

> #define MAX_PLUGINOUTPUT_LENGTH            352

Russell, that value, plus 160 bytes of miscellanous stuff, equals 512
bytes (that's not the interesting part).

The interesting part is that's the max size for atomic read/write
operations on a names pipe in Linux.

On my Solaris Nagios box, it's 5120 for the same atomic operation size
limitation, so I bumped up all the relevant stuff by 1024 bytes, and it
works fine.

I'm not sure where the perfdata would be carried in this case.  If it goes
through the names pipe (probably), it may cause big problems if you're
reading and writing to and from the command file in chunks bigger than 512
bytes...

Unfortunately, it's going to be hard to verify if there is (or isn't) a
real problem, if you make the change.  You may end up with command-file
commands being mangled, but maybe so infrequently that you could discount
them...  Maybe...

---
Jason Marshall, Unix Geek, Kelman Technologies, Inc., Calgary, AB, Canada.

  From a Sun Microsystems bug report (#4102680):
    "Workaround: don't pound on the mouse like a wild monkey."

  "I have great faith in fools: 
     Self confidence my friends call it."  -Edgar Allan Poe




-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
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