ASP .Net multiple Application Pools, and log file locking

[Marvin Addison]

>
> Doesn't sound like a big ask really.  Could be done simply by defining a
> new log appender class, derived from RollingFileAppender, but that opens
> and closes the file for each append.


The logback engine has a "prudent" flag to provide this sort of behavior,
so I don't think it's an unreasonable capability to want. It has, as you
noted, considerable negative impact on performance.

Have you considered NTEventLogAppender as a workaround?

Keeping open files handles for long periods is a BAD THING as it also
> prevents you clearing up log files manually.
>

I think it's important to note that that behavior is a platform-specific
problem. There's no such issue on Unix platforms, and it's common on those
platforms for services to hold file handles for hours if not days.

M <dev-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150806/23c22e26/attachment-0001.html>