logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-164) using a named mutex for file appenders
Date Wed, 07 Sep 2011 09:27:09 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098802#comment-13098802

Stefan Bodewig commented on LOG4NET-164:

I've added simple tests in svn revision 1166079 and made them pass.  Obviously the third arg
of CreateStream was expected to be used in the FileStream constructor.

So now the main remaining issue is naming (and documentation).

> 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
>         Attachments: MutexProcessLock.patch
>   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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message