2011/1/26 nap <naparuba@gmail.com>

2011/1/26 Albéric de Pertat <alberic@depertat.net>

2011/1/26 nap <naparuba@gmail.com>


Like I said, nrpy is a standalone daemon like nrpe is, and check_nrpy is a standalone "binary". It should be usable out of the box. About integrating it inside shinken, I don't know enough about the general infrastructure to answer that.
In fact for the client, the goal is to bypass a fork, and so give this nrpe lib to the "workers" (python process that really do the job) so they can just load it, launch the connexion without having to fork/Popen a process for it. I think we can expect huge performances for this :)

For the daemon, it can be a very good base for an enhanced agent. But it's far harder that just a "worker call" :p

I see what you mean. In both cases you would be able to get rid of all the old "90's code heaviness" , so I guess in the case that is a good thing.

By the way, the git can be cloned with :

  git clone http://nrpy.depertat.net/nrpy.git


Albéric de Pertat