[Nagiosplug-devel] Perf Data

[Karl DeBisschop]

On Thu, 2003-02-20 at 00:47, Ethan Galstad wrote:
> On 19 Feb 2003 at 13:16, Richard Colley wrote:
> 
> > It would seem to me that relying on something like atomic write sizes is
> > something of a hack.
> 
> Agreed, but its simple. :-)
> 
> > 
> > Maybe it is time to wrap the named external command pipe with an API that
> > serialises messages into the pipe.
> 
> That could get pretty ugly and you would loose the benefit of a 
> simple interface for external apps to use.  A better solution would 
> probably be to implement it as a unix domain socket instead of a 
> FIFO.
> 
> > 
> > Also, a simpler way of fixing this issue for the internal non-named pipes
> > from Nagios to children would be to have one pipe per child.  Given the
> > number of children that would normally be active simultaneously, this
> > shouldn't be a major issue.
> 
> Yep, I'll take a look at implementing this in 2.0

In a sense, this doesn't help though. Since the named pipe still has the
limits, the plugins still need to check their length, right?

I know nagios will truncate. but that is a problem if truncation leads
to unbalance HTML, or to altered perf data.

--
Karl