-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ton Voon wrote:
> Hi Ethan,
>
> We've found a problem with NSCA when aggregate writes are enabled and
> NSCA starts writing to the command file before it gets created.
> Details here: http://altinity.blogs.com/dotorg/2008/0 ... egate.html
Alternatively, Nagios could leave the pipe here and have nsca open the
file in non-blocking read-write - it will then be able to fill up the
pipe and Nagios will get the queued commands when it starts up. On write
failures (pipe full) the dump file could be used. This would be the
preferred method to avoid data loss.
That's pretty much the same as host/service_perfdata_file_mode=p in
Nagios 3 with a daemon like OCP_Daemon to get the data, but the other
way round.
- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHg8Vz6dZ+Kt5BchYRAgyfAJ0Ya6YR+DXZydCAFnDf80KrlMBO7wCg/IgR
WqVovkd5ekbogibtcz//g0E=
=MQca
-----END PGP SIGNATURE-----
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]