-
From: Nicko Cadell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 08, 2005 3:27 AM
To: Log4NET User
Subject: RE: File Access Error with RollingFileAppender
Mark,
It sounds like the configuration may not be loading correctly.
Can you enable internal debug and recreate the situation.
http
age-
> From: Stewart, Mark (GE Consumer Finance, consultant)
> [mailto:[EMAIL PROTECTED]
> Sent: 03 June 2005 16:34
> To: Log4NET User
> Cc: Gareth Mc Leigh
> Subject: RE: File Access Error with RollingFileAppender
>
> Thanks for the rapid replies!
>
> I dow
Nicko,
On 6/3/05, Nicko Cadell <[EMAIL PROTECTED]> wrote:
>
> The is only supported in log4net 1.2.9 and above. In
> 1.2.0 Beta 8 the output file is being locked exclusively by the first
> appender to be configured. Can you try upgrading to 1.2.9 which has
> support for the file appender locking
bool isDebugEnabled = log.IsDebugEnabled;
private static readonly bool isInfoEnabled = log.IsInfoEnabled;
}
Any ideas on this?
Thanks,
Mark Stewart
-Original Message-
From: Nicko Cadell [mailto:[EMAIL PROTECTED]
Sent: Friday, June 03, 2005 7:30 AM
To: Log4NET User
Subject: RE: Fi
Mark,
The is only supported in log4net 1.2.9 and above. In
1.2.0 Beta 8 the output file is being locked exclusively by the first
appender to be configured. Can you try upgrading to 1.2.9 which has
support for the file appender locking models.
Cheers,
Nicko
> -Original Message-
> From:
I had a similar problem with "because it is being used by another process".
Probably got nothing to do with yours but I was using the wrong
debug/release reference file.
From: "Stewart, Mark (GE Consumer Finance, consultant)"
<[EMAIL PROTECTED]>
Reply-To: "Log4NET User"
To:
Subject: File Ac
