Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.2.14, 1.3.0
-
None
-
None
Description
The only missing feature is an option for choosing Local (per session) or Global (per machine) mutex.
The current code just uses the filename for mutex which good but it always makes a local one, so if you have two sessions you cannot synchronize them.
Default is Local for backward compatibility.
See Note in: https://msdn.microsoft.com/en-us/library/system.threading.mutex%28v=vs.110%29.aspx
I think it can be an option like
<RollingMutexType value="Global" />
or something like that.
It also applies to FileAppender mutex .
<LockingModel InterProcessLock>
<LockingMutexType value="Global" />
</..>
See issue #485 for reference.
Attachments
Issue Links
- is duplicated by
-
LOG4NET-500 1.2.15 RollingFileAppender is 60% slower than 1.2.11
- Closed
- is required by
-
LOG4NET-506 RollingFileAppender locking log folder in some cases
- Open
- relates to
-
LOG4NET-611 Failed to create netstandard version of logger
- Closed
-
LOG4NET-347 Log4net not working in an ASP.Net environment with medium trust
- Closed