I have just committed updates to the "linelog" module (including documentation) that significantly increase it's usability. The goal is to move most of the hard-coded log messages to this module. Once these log messages are added to the configuration, the existing hard-coded messages can be deleted. We're looking for volunteers to examine the existing log messages, and to submit sample one-line log formats for the "linelog" module. Alan DeKok.
Alan DeKok wrote:
I have just committed updates to the "linelog" module (including documentation) that significantly increase it's usability. The goal is to move most of the hard-coded log messages to this module. Once these log messages are added to the configuration, the existing hard-coded messages can be deleted.
Ok, so you're talking about removing all DEBUG() and other logging function calls from the source and replacing it all with soft configuration based logging ? Or just specific ones ? Are you no longer committing to CVS btw ?
We're looking for volunteers to examine the existing log messages, and to submit sample one-line log formats for the "linelog" module.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Arran Cudbard-Bell wrote:
Ok, so you're talking about removing all DEBUG() and other logging function calls from the source and replacing it all with soft configuration based logging ? Or just specific ones ?
No! The DEBUG logs will still be there. I'm talking about the hard-coded logs like "login OK", or "login failed".
Are you no longer committing to CVS btw ?
Yes. See http://git.freeradius.org. I'll get gitweb set up soon, too. Git is harder to learn than Mercurial. But it beats the heck out of CVS. Alan DeKok.
participants (2)
-
Alan DeKok -
Arran Cudbard-Bell