Yep ;) But as said, this will perhaps imply huge code modification in satellites to permit log messages to be logged locally and/or sent to broker.
Laurent Le jeudi 06 janvier 2011 à 09:52 +0100, nap a écrit : > Yep, the broker way is cool for getting a common log file, but in the > begining, got local logs to see what is bad in the > configuration/architecture can be useful. I think I'll add a > "local_log" parameter in the etc/*d.ini files with void default value. > So if the user want local log, he just need to enable it (so you see > why a log module don't load for example ;) ). > > > Jean > > On Wed, Jan 5, 2011 at 6:39 PM, Hartmut Goebel > <[email protected]> wrote: > Am 05.01.2011 18:17, schrieb Laurent Guyon: > > Is it possible to enable standard log on each daemon (stored > in a local > > log file, or better sent to the local syslog) without using > a broker ? > > For example to see standard working messages, or tracebacks > when error > > occur... > > On my personal, unpublished and undiscussed roadmap there is a > point > "using standard module logging for logging". But this is quite > a big > change, so we'll have to discuss it in depth first. > ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Shinken-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shinken-devel
