John Peacock said the following on 25/11/2005 19:44:
> Robin Bowes wrote:
> 
>>Any suggestions as to the best way to log all this information on a
>>single line so it can be easily parsed by a script for statistical purposes?
> 
> 
> When I wrote the adaptive logging feature, I wasn't concerning myself with
> parsability of the log lines because they are emitted by various and sundry
> plugins (which each log different things).  If you really want to make the 
> line
> parseable, you probably want to quote the terms (i.e. quote and comma 
> delimited).
> 
> However, that seems like an awful lot of different fields to log (for most
> people), so I'm not sure that we should include that as a default output.  How
> about cutting that out and making it a config file option.  Then it would be
> easy to eval() the contents of the config file itself to generate the log 
> line.
>  I'll know more when I see what you have already started working on...

OK, I'll tidy things up and post what I've got so far.

I'm currently writing for what *I* will find useful so what's best for
default output is probably up for discussion.

New bikeshed anyone?

R.
-- 
http://robinbowes.com

If a man speaks in a forest,
and his wife's not there,
is he still wrong?

Reply via email to