I've been able to get the syslog appender to work, with one exception.
For our Java apps that use log4j, I have set up a custom entry in
/etc/syslog.conf for the local7 facility so that messages targeting this
facility are all logged to a custom log file. In my log4j config file I
simply have to
On Thu, Jun 5, 2008 at 10:39 AM, Peter Steele [EMAIL PROTECTED] wrote:
I've been able to get the syslog appender to work, with one exception.
For our Java apps that use log4j, I have set up a custom entry in
/etc/syslog.conf for the local7 facility so that messages targeting this
facility are
That is a bug in version 0.10.0 Local 2 and higher was not implemented
correctly. See this difference to see the cut-and-paste error:
http://svn.apache.org/viewvc/logging/log4cxx/trunk/src/main/cpp/syslog
appender.cpp?r1=613005r2=654960pathrev=654960diff_format=l
It has already been fixed in the
This is what we're doing right now and it appears to be working fine. Is
this safe to do though, as a general rule?
On Thu, Jun 5, 2008 at 2:00 PM, Peter Steele [EMAIL PROTECTED] wrote:
That is a bug in version 0.10.0 Local 2 and higher was not implemented
correctly. See this difference to see the cut-and-paste error:
http://svn.apache.org/viewvc/logging/log4cxx/trunk/src/main/cpp/syslog
On Jun 5, 2008, at 1:23 PM, Stephen Bartnikowski wrote:
I've been doing that for two years with no issue. It was my
understanding that this was one of the major features of log4cxx,
but I could be taking that for granted.
- Stephen
From: Peter Steele [mailto:[EMAIL PROTECTED]
Sent:
On Thu, Jun 5, 2008 at 10:18 PM, Curt Arnold [EMAIL PROTECTED] wrote:
On Jun 5, 2008, at 12:55 PM, Dale King wrote:
That is a bug in version 0.10.0 Local 2 and higher was not implemented
correctly. See this difference to see the cut-and-paste error:
