logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kamen Dimitrov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files.
Date Tue, 17 Jul 2012 14:07:35 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416225#comment-13416225
] 

Kamen Dimitrov commented on LOG4NET-27:
---------------------------------------

I did download the source and looked at all the attached files and took the source from there,
and build the project. I took the log4net.dll, and I've tried it locally to see if it is going
to work, but it didn't, so it might be a problem with the source that I build or it might
be misconfiguration on my side. Unfortunately because I'm not sure how should the config file
that is using the log4net.dll I can't confirm anything, that's why I was wondering if someone
has made it work, so he can upload all the files.
                
> Rolling files on date/time boundaries doesn't support a maximum number of backup files.
> ---------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-27
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-27
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.11
>            Reporter: Florian Ramillien
>            Priority: Minor
>             Fix For: 1.2 Maintenance Release
>
>         Attachments: LOG4NET-27.patch, RollingFileAppender.cs, RollingFileAppender.cs,
RollingFileAppender.cs, RollingFileAppender.cs.patch, RollingFileAppender.patch
>
>
> A maximum of backup files exist when rolling files on file size, but not for rolling
on date/time.
> This can be implemented with the same config key : MaxSizeRollBackups

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message