[Nagiosplug-devel] Please can I have GIT access

[Thomas Guyot-Sionnest]

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

Alain Williams wrote:
> On Tue, Sep 01, 2009 at 12:21:28PM -0400, Max wrote:
>> On Tue, Sep 1, 2009 at 11:22 AM, Thomas Guyot-Sionnest <dermoth at aei.ca> wrote:
>>> Back to the data retention debate, I agree if we go that way functions
>>> could be used for state retention. Another thing we could consider
>>> (although I believe you don't like it much) is shared memory...
>> Files in RAM or memcache is a lot easier to manage than shared memory.
> 
> Files:
> 
> * easy to set up, flexible
> * don't use up RAM - some sites RAM is precious
> * those who do want the speed of RAM, simply create a RAM disk or tmpfs and put the
>   files there
> * if it is a 'disk' directory and the system is not hard pressed on RAM, the files
>   end up in RAM anyway (buffer cache)

Just for completeness the FD method uses files primarily, but it
actually gives that control to the caller. This means:

 * Plugin only cares about FD numbers to use, caller decides where data
will go. No extra work, library or complex code required in the plugins.
 * If desired, caller can send FDs pointing to mmaped memory, and then
decide where to store it afterward (private RAM, SHM, memcached, SQL...)
 * Any custom wrapper can be used, for any desired retention method.
 * Nagios and NRPE could provide basic methods for simple setups and to
avoid an extra fork. Furthermore Nagios modules could be used to extend
Nagios functionality in an efficient manner on large sites.

I believe this method is much closer to the Unix philosophy of having
multiple components doing simple tasks.

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

iEYEARECAAYFAkqdcscACgkQ6dZ+Kt5BchabQACg9gM8qCcpFfI4UEWNlGum8+Md
EQQAn3TEqvTVF8zpqZSouVpZyLFEoPRX
=pYTp
-----END PGP SIGNATURE-----