[
https://issues.apache.org/jira/browse/LOG4NET-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628920#comment-16628920
]
Andrei Stryia commented on LOG4NET-487:
---------------------------------------
I've updated AssemblyInfo.cs with the following code (differ a bit from yours
suggestion)
{code}
#if (!(NETCF || NETSTANDARD1_3))
//
// If log4net is strongly named it still allows partially trusted callers
//
[assembly: System.Security.AllowPartiallyTrustedCallers]
#endif
{code}
And the issue disappeared.
> Control mutex type
> ------------------
>
> Key: LOG4NET-487
> URL: https://issues.apache.org/jira/browse/LOG4NET-487
> Project: Log4net
> Issue Type: Improvement
> Components: Appenders
> Affects Versions: 1.2.14, 1.3.0
> Reporter: NN
> Assignee: Dominik Psenner
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
