Re: controlling the status logger output?

ome throttling but can't be sure. > > .. > > I guess we could write our own application which takes stdin and writes to > files and this could do the rolling file work. I would think something like > that might already exist in linux. > > Thanks, > Nick &

RE: controlling the status logger output?

ubject: RE: controlling the status logger output? Date: Mon, 7 Mar 2016 11:19:59 -0500 I was asking about what's getting logged as I figured we shouldn't have that much in there to be too worried about disk space consumption. The appender in question is an https appender we wrote. If it

Re: controlling the status logger output?

rlier and > noticed some throttling but can't be sure. > > .. > > I guess we could write our own application which takes stdin and writes to > files and this could do the rolling file work. I would think something like > that might already exist in linux. > > Thanks,

Re: controlling the status logger output?

On Mon, Mar 7, 2016 at 11:19 AM, Nicholas Duane wrote: > I guess we could write our own application which takes stdin and writes to > files and this could do the rolling file work. I would think something > like that might already exist in linux. > > Thanks, > Nick > take a

RE: controlling the status logger output?

already exist in linux. Thanks, Nick > Subject: Re: controlling the status logger output? > From: ralph.go...@dslextreme.com > Date: Mon, 7 Mar 2016 08:54:05 -0700 > To: log4j-user@logging.apache.org > > If you set the status level to ERROR the StatusLogger should generate ver

Re: controlling the status logger output?

If you set the status level to ERROR the StatusLogger should generate very little output. That said, if you are concerned you can redirect stdout and implement the rolling yourself. Ralph > On Mar 7, 2016, at 8:39 AM, Nicholas Duane wrote: > > We've written some appenders and

Re: controlling the status logger output?

The only thing I can think of is logrotate, but I'm not sure if that would work properly. StatusLogger is intentionally simple so that it will always work regardless of the rest of the system. On 7 March 2016 at 09:39, Nicholas Duane wrote: > We've written some appenders and I

controlling the status logger output?

We've written some appenders and I think the prescribed approach is to use the status logger in log4j2 components, is that correct? The problem we're running into is that we redirect stdout to a file and thus that file can grow unbounded. It seems there's no way to have something like a