logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From renny.ko...@rubixinfotech.com
Subject RE: How to config log4cxx to delete the log files periodically
Date Wed, 17 Sep 2008 12:48:46 GMT
Again, this is my opinion:  I would suppose that would be the case... 
however, from an OOAD perspective, DailyRollingFileAppender deleting files 
would end up being a dichotomy in the use-case of a "FileAppender".   I 
would suggest you setup a ExpiredFileManager or something that sets up its 
own timer, or alarm, and processes the old files.... if you want to do it 
from within your process.

Renny Koshy

Jathy <xuehai.fan@yahoo.com> 
09/17/2008 06:30 AM
Please respond to
"Log4CXX User" <log4cxx-user@logging.apache.org>


RE: How to config log4cxx to delete the log files periodically

Thanks all.
Does it mean I must extend DailyRollingFileAppender class if I want to 
such goal?

renny.koshy wrote:
> From what I've seen out there... small biz to large enterprises is that 
> for System Admins, they see deleting logfiles as part of a global task 
> that they generally set-up as part most large-scale enterprise systems. 
> They prefer to have one point that manages all historical data, 
> etc. and do not really appreciate when a process deletes its logfiles. 
> Specifically, we have customers who maintain logs for 3 days and some 
> up to 30 days, and some that archive old logs for compliance/audit 
> purposes.
> So... while I agree that a listener interface that one can register for 
> log rotation would be nice, IMHO most large-scale uses of Log4CXX would 
> not be able to use that to delete log file...
> Regards,
> Renny Koshy
> Conway Allen <Allen.Conway@atosorigin.com> 
> 09/16/2008 09:19 AM
> Please respond to
> "Log4CXX User" <log4cxx-user@logging.apache.org>
> To
> Log4CXX User <log4cxx-user@logging.apache.org>
> cc
> Subject
> RE: How to config log4cxx to delete the log files periodically
> I suppose that if it were possible to define a callback that would be 
> invoked when a roll-over takes place it would be possible to do the kind 

> of housekeeping he wants without needing to use the crontab…
> regards, Allen.
> From: Dale King [mailto:dalewking@gmail.com] 
> Sent: Saturday, September 13, 2008 4:20 PM
> To: Log4CXX User
> Subject: Re: How to config log4cxx to delete the log files periodically
> Log4Cxx does not have this capability. It only lets you specify a max 
> number of files when using the size based rolling policy. This is not an 

> arbitrary decision. There is no good way to accomplish what you want. 
> is log4cxx supposed to know what files it can delete? Log4cxx maintains 
> history of what files it has created in the past.
> I suggest you create a daily job that deletes log files that are more 
> 31 days old based on creation date.
> On Fri, Sep 12, 2008 at 2:45 AM, Jathy <xuehai.fan@yahoo.com> wrote:
> Anybody has any idea about the below question? Waiting online...
> Jathy wrote:
>> Hi All,
>> In my project, I need produce one log file per day and delete the log
>> files periodically so that at most 31 files are stored. I used
>> DailyRollingFileAppender, it helped me to reach my first goal easily. 
> But
>> how to config it to delete the log files automatically? Thanks.
>> Regard,
>> Jathy
> --
> View this message in context: 

> Sent from the Log4cxx - Users mailing list archive at Nabble.com.
> -- 
> Dale King
> Ce message et les pièces jointes sont confidentiels et réservés à 
> exclusif de ses destinataires. Il peut également être protégé par le 
> secret professionnel. Si vous recevez ce message par erreur, merci d'en 
> avertir immédiatement l'expéditeur et de le détruire. L'intégrité du 
> message ne pouvant être assurée sur Internet, la responsabilité du 
> Atos Origin ne pourra être recherchée quant au contenu de ce message. 
> que les meilleurs efforts soient faits pour maintenir cette transmission 

> exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard 

> et sa responsabilité ne saurait être recherchée pour tout dommage 
> résultant d'un virus transmis.
> This e-mail and the documents attached are confidential and intended 
> solely for the addressee; it may also be privileged. If you receive this 

> e-mail in error, please notify the sender immediately and destroy it. As 

> its integrity cannot be secured on the Internet, the Atos Origin group 
> liability cannot be triggered for the message content. Although the 
> endeavours to maintain a computer virus-free network, the sender does 
> warrant that this transmission is virus-free and will not be liable for 
> any damages resulting from any virus transmitted.

View this message in context: 

Sent from the Log4cxx - Users mailing list archive at Nabble.com.

View raw message