Yep. But are we ok at how we manage this from the poller point of view?
I don't know if we need a new check interface if we manage the PollerModule
as a standalone worker. I think this last one sould :
* have a main() like current (fork) workers, so get from a Queue Checks, and
then run them.
* have a run(Check) method
With this, the module can be blocking or not for the call, it do not matter
for others, and with the run(Check) call, we sill have a way to call it from
a generic shell command.
Is it ok or do you thing to something else?
Jean
On Wed, Feb 2, 2011 at 11:35 AM, Gerhard Lausser
<gerhard.laus...@consol.de>wrote:
>
> > unless someone has begun the work on this : I'm all open to
> > do this as I manage quite very well that part of the code ..
> i didn't have the time, so it'll be fine if you could care for it.
>
> Gerhard
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
