ops.log: feedback requested

All,

Recently, we changed log4j.xml to have this definition by default:

   <appender-ref ref="SingleFileAppender"/>

with the appender pointing to:

   <param name="File" value="../logs/ops.log"/>

This works great when:

* You use Tomcat
* You start Tomcat from its bin directory

The benefit is that you get a log file in the right place.

The drawback is that if you are not in the above situation, you get an
exception during startup. This is not fatal, but it's not pretty either.

Can anybody see a better solution? Should be simply revert back to not
enabling the SingleFileAppender by default?

See also the bug entry:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=307092&group_id=168&atid=350207

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Erik,
    Personally I don't use the file appender locally, instead I use the OPSMonitor, because I can easily filter the results etc. However we do use the SingleFileAppender on some of our Unix Development environments, but only when we don't have access to the OPSMonitor and we then use full directory paths because we have a lot of log files.

Because we use our own log4j.xml it makes no difference about the default, this is just my 2c.

Ryan


Erik Bruchez wrote:

All,

Recently, we changed log4j.xml to have this definition by default:

  <appender-ref ref="SingleFileAppender"/>

with the appender pointing to:

  <param name="File" value="../logs/ops.log"/>

This works great when:

* You use Tomcat
* You start Tomcat from its bin directory

The benefit is that you get a log file in the right place.

The drawback is that if you are not in the above situation, you get an exception during startup. This is not fatal, but it's not pretty either.

Can anybody see a better solution? Should be simply revert back to not enabling the SingleFileAppender by default?

See also the bug entry:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=307092&group_id=168&atid=350207

-Erik

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws