Am 20.08.2012 04:00, schrieb Francois Mikus:
> Answering myself is strange but hey, I am confused.

Please do not spent time analysing the logging. I've already done quite
some work on this.

I have an idea (and a draft implementation) on how to switch to the
standard Python logging modules. This would solve many of the problems
you found. Unfortunately my spare time is rare currently and I had to
eliminate all usage of logger.log() first, as this conflicts with the
standard logger.

I've just published pull-request #532 for eliminating .log(). If this is
accepted and Jenkins does not show up errors, I'll continue with the new
logging module.

So please be patient just a few more days :-)

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goe...@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to