I've made that suggestion myself. In setFile() of CompositeRollingAppender I
added:
if (!staticLogFileName)
scheduledFilename = fileName = fileName.trim() + sdf.format(now);
I believe that adding the assignment line to the DailyRollingFileAppender will
do the trick though I haven't tested it in that class. Or you could use
CompositeRollingAppender which has an option to do what you're asking.
Kevin
"ONG CHIN HUI, C21PgM" wrote:
> >Hi all,
> >
> In our environment, we have a lot of processes that need to log >events to
> files on a daily or hourly basis. The DailyRollingFileAppender is
> appropriate for such logging. However, the behavior of naming the log file
> may cause some problems.
>
> Below is extracted from the javadoc of DailyRollingFileAppender:
>
> For example, if the File option is set to /foo/bar.log and the DatePattern
> set to '.'yyyy-MM-dd, on 2001-02-16 at midnight, the logging file
> /foo/bar.log will be copied to /foo/bar.log.2001-02-16 and logging for
> 2001-02-17 will continue in /foo/bar.log until it rolls over the next day.
>
> For short-lived processes or cases when the server is down, the log files
> may not be renamed.
>
> IMHO, why don't we simply open the log file with the date time extension ?
> >
> >Regards.
>
> This communication contains confidential or privileged information. If you
> are not the intended recipient, please notify us IMMEDIATELY that you have
> received it and destroy it. We are not liable for any unauthorised sending
> of or interference with this communication.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
