...@gmail.com] On Behalf Of Curt Arnold
Sent: Monday, September 12, 2011 00:40
To: Log4NET Dev
Subject: Re: The state of RollingFileAppender
The rolling file appenders are the single greatest cause of recurring
problems in log4j and all those problems have been inherited by log4net.
I don't
[mailto:bode...@apache.org]
Sent: Monday, September 12, 2011 05:43
To: log4net-dev@logging.apache.org
Subject: Re: The state of RollingFileAppender
On 2011-09-12, Roy Chastain wrote:
> When I looked at this code a few years ago, I thought it was overly
> complicated and obtuse. Since spending t
On 2011-09-12, Curt Arnold wrote:
> The rolling file appenders are the single greatest cause of recurring
> problems in log4j and all those problems have been inherited by
> log4net.
Quite possible. RollingFileAppender is responsible for more than 10% of
all open log4net issues right now.
> The
On 2011-09-12, Roy Chastain wrote:
> When I looked at this code a few years ago, I thought it was overly
> complicated and obtuse. Since spending the day with it today, and
> discovering the invalid assumption, I stand by my original opinion.
I was afraid you'd say that when you volunteered to l
The rolling file appenders are the single greatest cause of recurring problems
in log4j and all those problems have been inherited by log4net.
I don't think that the rolling file appenders are fixable. Any approach that
involves systematic renaming for files is not going to be robust. Even a si
Lines 30 - 40 indicate an assumption that someone made as to how file
access works. I do not know if they ever proved their assumption at the
time, but under windows 7 and .NET framework 4.0, the assumption is
incorrect.
The only time you that you may "move" an open file, is if it was opened
with
