Re: redefining existing levels?
Ralph Goers <ralph.goers <at> dslextreme.com>
2015-08-26 16:29:52 GMT
Well, I suppose we could add a minimum logging level system property and if someone tries to set the level
lower than that then the minimum level gets used instead. But I’m not really crazy about that as it could
cause all kinds of “unexpected” consequences when processing the configuration.
It seems to me that the real issue is that people have access to your production machines who probably shouldn’t.
> On Aug 26, 2015, at 9:24 AM, Gary Gregory <garydgregory <at> gmail.com> wrote:
> On Wed, Aug 26, 2015 at 9:19 AM, Nicholas Duane <nickdu <at> msn.com <mailto:nickdu <at> msn.com>> wrote:
>> I guess the main use case we're trying to solve is someone, maybe some
>> admin or maybe a developer asking the admin, thinking they should turn
>> logging off and thus sets the level to "OFF". We always want INFO and more
>> critical levels to be on no matter what.
> But if a user gets in a config file and sets the root level to off, how can
> you stop him or her from removing your filters and custom levels?
>>> Subject: Re: redefining existing levels?
>>> To: log4j-user <at> logging.apache.org
>>> From: xen <at> dds.nl