Hi,
On Thu, Aug 23, 2012 at 10:01 PM, Hartmut Goebel <
h.goe...@crazy-compilers.com> wrote:
> Hi,
>
> [...]
>
> 1) Should messages go to stdout/stderr by default?
>
> IMHO messages should go to stdout or stderr *only* in two cases:
>
> a) While rading the config-file
> b) If the user runs the daemon with some "--verbose" option.
>
That's the --debug option I think. In the other cases (without it) in fact
the daemonize function will close the file descriptors 0 and 1. With
--debug, it will link theses FDs to the debug file.
>
> 2) Should messages send via broks be terminated by '\n'?
>
> IMHO this is useless as it most probably will be stripped at the
> receiver anyway. (I did not check the source.)
>
Good point, I don't remember. I think keeping the \n won't hurt so we don't
have to make a difference between print versions and brok ones.
>
> 3) Are level-names allowed to be upper-case? Or is there any program
> known to rely on these to be capitalized text?
>
> Currently they are capitalized, but the standard logging module uses
> upper-case names. If capitalized are required, we need to dig deeper
> into the code.
>
All Nagios related tools are using upper cases logs, because it's how the
classic WARNING, CRITICAL logs are.
>
> 4) Should all messages (above the set level) be send to the broker,
> even e.g. those about reading the config file?
>
Yes, because it's always good to see which configuration files you are
reading, and what is the current working directory of your daemon, and your
Pyro URI, etc etc. such informations are very useful.
>
> 5) Do we need 'human format' for messages send as broks, too?
>
I think the human format was an error, and we should never allow such
"format" at the beginning. We can send them, they won't be readable by
tools, but the comment on this parameter is clear about that :)
Jean
------------------------------------------------------------------------------
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
