Hi,last year we decided on the workshop to completely rewrite the logging stuff. Now it is time to talk about the details. Ok, I don't expect that now everybody starts hacking it's own log implementation but we only decided to use syslog for authentication issues and the database for all issues. The big question is what do we want in the log?
A syslog can only log the following: time (automatically created) ident (the name of the daemon for example) facility (e.g. auth, local7, user) priority (e.g. crit, err, warning, info) message Syslog-ng is a little bit better: host facility priority/level (same only other name) tag (hex encoded facility and priority - for filtering) date/time/TZ program msgA database is much more flexible but the question is should we have an interface/database design which is like a syslog facility or should we add more details? I think it is a good idea to be as simple as possible here.
So my favorite would be an interface in the style of syslog-ng. I would like to throw away the XML logging of openca 0.9.2. (An idea in the background is the easy integration with monitoring systems like nagios, tivoli or hp openview.)
Any comments or other ideas? Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
