Seems useful. Just a few questions.... When Append="true" I presume the header will get written again, right? So, it wouldn't just exist on the first line of the log file, but on the first line of logging per appender configuration pointing at a given log file. Also, in the example, you don't use HeaderPattern. I guess there's a default provided, given the output after the FirstLine and SecondLine info?
BTW, are you looking to include this in the official Log4j project (either in the main jar or extras companion)? I'm not saying you should or should not. Just curious. If so, one issue might be the dependency on "Debug String Utils" and "Container Detector" projects. Jake Lilianne E. Blaze wrote: > Hello, > Guys? I'd really appreciate _some_ feedback? > > Greetings, Lilianne > > Lilianne E. Blaze wrote: >> Hello, >> Could you please take a look at >> http://www.lilianne-blaze.net/wiki/bin/Java/HeaderPatternLayout ? >> >> Mostly inspired by http://juliusdavies.ca/logging.html (search for "A >> Log Rotation Best Practice"). The general idea is to write a line on >> top (and optionally end) of every log file with basic information >> about the current environment, like memory, Java runtime and VM info, >> operating system, etc. >> >> Any feedback, comments, suggestions, questions, would be most welcome. >> >> Greetings, Lilianne E. Blaze >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
