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 "Nicko Cadell (JIRA)" <ji...@apache.org> on 2005/08/30 00:50:06 UTC

[jira] Resolved: (LOG4NET-3) Support per event patterns in FileAppender File name

     [ http://issues.apache.org/jira/browse/LOG4NET-3?page=all ]
     
Nicko Cadell resolved LOG4NET-3:
--------------------------------

    Fix Version: 1.2.10
     Resolution: Fixed
      Assign To: Nicko Cadell

The log4net.Util.PatternString type allows patterns to be specified in the FileAppender File property at configuration time. This can be used to allow multiple copies of the same application to log to separate log files.

There is also an example appender in the SampleAppendersApp that allows event specific patterns to be used in the file name. The appender constructs the file name for each event using a PatternLayout, the file is opened and closed for each event.

For more details see
examples\net\1.0\Appenders\SampleAppendersApp\cs\src\Appender\PatternFileAppender.cs

> Support per event patterns in FileAppender File name
> ----------------------------------------------------
>
>          Key: LOG4NET-3
>          URL: http://issues.apache.org/jira/browse/LOG4NET-3
>      Project: Log4net
>         Type: Improvement
>   Components: Appenders
>     Versions: 1.2.9
>  Environment: From sourceforge: 812999
>     Reporter: Nicko Cadell
>     Assignee: Nicko Cadell
>      Fix For: 1.2.10

>
> If I could specify file name patter for
> (Rolling)FileAppender that would be filled by the
> appender prior to openning the file, I could let many
> individuals run the same applikation (on terminal
> server) and still log to file (not RemotingAppender or
> ADONetAppernder)
> I guess, pattern like &quot;rootLog%U.log&quot; would do, if
> appender replaced %U with
> Thread.CurrentThread.CurrentPrincipal.Identity.Name ...
> Or %T with thread id and so on...
> Anonymous

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira