By default, if you have a lot of size-rollings at one day, log4net has
to rename all backups every rolling time.
If you set CountDirection to 1, it'll only rename every new file ready
for rolling.
If you unset this StaticLogFileName flag, renaming will not be nesessary at all.
On Tue, Apr 27, 2010
Hm ok but why is one option better than the other? Should I care?
Yuriy Taraday wrote:
>
> Hi.
>
> If there's true, you always log to your example.log file, which is
> renamed as part of rollover procedure.
> If there's false, you always log to example.log.-MM-dd.N (in
> common case) file
Hi.
If there's true, you always log to your example.log file, which is
renamed as part of rollover procedure.
If there's false, you always log to example.log.-MM-dd.N (in
common case) file and rollover is just creating one more such file.
On Mon, Apr 26, 2010 at 5:39 PM, ITemplate wrote:
>
>
Hi,
I read this:
http://logging.apache.org/log4net/release/sdk/log4net.Appender.RollingFileAppender.StaticLogFileName.html
Plz don't laugh, but I don't understand that english :). Could someone
rephrase what that boolean means? What is the default value and should I
change that to true or false?
Thanks Ron, very interesting. That interface also explains why log4net
accepts an object - I like this. I will look into your suggestions, thanks.
--
Werner
Ron Grabowski wrote:
>
> Have you looked into writing an log4net.ObjectRenderer.IObjectRenderer to
> render the message as text or is t
