Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: pass (athena.apache.org: domain of boards@gmail.com designates
 209.85.214.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50C218D8-C6E1-4F77-8196-7DD311B486E6@dslextreme.com>
References: 
 <CAJ5ySLd8qZ+NegX+K8jMRBe6Zrsw1Oj9di-FtnryvAfH6DMMfA@mail.gmail.com>
	<50C218D8-C6E1-4F77-8196-7DD311B486E6@dslextreme.com>
Date: Wed, 9 Apr 2014 16:58:59 -0600
Message-ID: 
 <CACmp6kq6Qh8a8CJdk02e7oe5XG85gY=vg6sv7GbYguMy=SeUtw@mail.gmail.com>
Subject: Re: Compressing only old rollover files
From: Matt Sicker <boards@gmail.com>
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2cd18d00e6d04f6a40bba

--001a11c2cd18d00e6d04f6a40bba
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It sounds like the "delaycompress" option from logrotate:
http://linux.die.net/man/8/logrotate


On 9 April 2014 09:46, Ralph Goers <ralph.goers@dslextreme.com> wrote:

> Log4j currently compresses the files when it rolls them over. Of course
> you can cause that to happen based on time, but it sounds like you want t=
he
> time of rollover and time of compression to be separate.  If so, I am not
> sure you really need to tie the compression activity to Log4j, or at leas=
t
> the appender at all.  You just need something that monitors the directory
> and looks for files over a certain age and then compresses them, deletes
> them, or whatever.
>
> If I=E2=80=99ve misunderstood what you are asking please let me know.
>
> Ralph
>
> On Apr 9, 2014, at 12:57 AM, Manuel Teira <manuel.teira@gmail.com> wrote:
>
> > Hello all,
> >
> > I'm evaluating a switch to log4j-2 since my application is required to
> > rollover files by age and size (for what the composite triggering
> policies
> > come handy). The rollover files shall also be compressed, but only thos=
e
> > reaching a given age.
> >
> > What would be the preferred approach to achieve that using log4j-2?
> Should
> > be reasonable to write a custom rollover strategy or is there any other
> way
> > out-of-the box that may work?
> >
> > Thanks and best regards,
> >
> > Manuel.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>


--=20
Matt Sicker <boards@gmail.com>

--001a11c2cd18d00e6d04f6a40bba--