gmane.comp.apache.logging.log4net.devel

Frank (JIRA | 9 Jul 14:33

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

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

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.

headers

Ron Grabowski (JIRA | 10 Jul 06:59

[jira] Updated: (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 updated LOG4NET-164:
----------------------------------

    Fix Version/s: 1.2.11

Yep...someone already posted some code they're using:

 http://www.mail-archive.com/log4net-user <at> logging.apache.org/msg04116.html

I think we need to get them to upload the patch to JIRA and mark it as being ok to include in the code base or else
we'll have to re-implement it.

> 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
>             Fix For: 1.2.11
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>

(Continue reading)