Re: log4j and logrotate
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matthew Johnson wrote:
> On Mon Feb 15 11:35, Thomas Koch wrote:
>> what's preferred?
>>
>> - use log4j's internal logrotate mechanism
>> - use debian's logrotate
>>
>> And if debian's is prefered, how to do it properly, so that log4j won't
>> complain or continue writing in a just rotated logfile?
>
> If it's easy to do (not significant upstream patching etc) then I'd favour the
> system logrotate. Normally this works by HUPing the program to reopen it's log
> files, but I don't know now log4j does this.
Since log4j is a library that can be used any Java app (and not only daemons)
and supports various types of appenders, I'm not sure logrotate will always
applicable. Also, I think the patching to log4j would be non-trivial.
- From the perspective of someone supporting systems that use log4j, I'd say that
it might be disconcerting for users to have both log4j and logrotate managing
the same logfiles.
What's the context of the question? Is this for a specific package, or in
general (for all Debian Java packages)?
Cheers,
Tony
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkt5gxEACgkQpdwBkPlyvgPjNgCcD4mS7xhqcuLEUqu9uF6/4mKb
D8YAn3eHbps1GGllF2DK8kIfjQOS7z9t
=BE1n
-----END PGP SIGNATURE-----
Reply to: