You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Ron Grabowski (JIRA)" <ji...@apache.org> on 2009/02/08 21:08:59 UTC

[jira] Assigned: (LOG4NET-164) using a named mutex for file appenders

     [ https://issues.apache.org/jira/browse/LOG4NET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Grabowski reassigned LOG4NET-164:
-------------------------------------

    Assignee: Ron Grabowski

> using a named mutex for file appenders
> --------------------------------------
>
>                 Key: LOG4NET-164
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-164
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>            Reporter: Frank
>            Assignee: Ron Grabowski
>             Fix For: 1.2.11
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> About logging to the same file from 2 or more instances of an application.
> As opposed to a minimallock which makes it still possible for 2 application instances to interfere. Why not use a named mutex so that the logging will wait for the lock to be released from another instance.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.