Hi Jon,

That is not normal growth, are there exceptions filling it up or is it all info?

You can configure (or disable) what level of logging is happening by editing /config/log4net.config More info on how to configure log4net http://logging.apache.org/log4net/release/manual/configuration.html For example you can set it to only contain error level or above.

Thanks,

Jeavon

I'm still learning Log4Net configuration settings, but I did see setting the priority from default INFO to now WARN and going to see how it fairs.  Using Log4View it's a lot of nHibernate messages and info that stuff is being published, this site has upwards to 5000 nodes.  Perhaps after the site goes live it will simmer down anyway.

Hi, just been looking at this and in umbraco log4net in umbraco is set to roll on dates not size if you want to limit the logfiles in size, then:

change rollingStyle to Size or Composite <rollingStyle value="Composite" /> this will cause the log file to roll over when the maximumFileSize is reached (5MB by default).

adding <maxSizeRollBackups value="5" /> will cause the last 5 versions of the log file to be kept so you can look back on things if you need too.

e.g.

<appender name="AsynchronousLog4NetAppender" type="Umbraco.Core.Logging.AsynchronousRollingFileAppender, Umbraco.Core">
        <file value="App_Data\Logs\UmbracoTraceLog.txt" />
        <lockingModel type="log4net.Appender.FileAppender+MinimalLock" />
        <appendToFile value="true" />
        <rollingStyle value="Composite" />
        <maximumFileSize value="5KB" />
    <maxSizeRollBackups value="10" />
        <layout type="log4net.Layout.PatternLayout">
            <conversionPattern value="%date [%thread] %-5level %logger - %message%newline" />
        </layout>
    </appender>

is working on a reply...