Re: Using the syslog appender in log4cxx

On Jun 5, 2008, at 11:10 PM, Dale King wrote: I saw that when you made the checkin, but I don't understand why you think it is only a cosmetic bug. It seems to me that if you were trying to configure a syslog appender for LOCAL2 for instance it would call setFacility with LOCAL2 as the facilit

Re: Using the syslog appender in log4cxx

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: >> >> >>

Re: Is it safe to has different processes on the same machine log to the same file?

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: Thursd

Re: Using the syslog appender in log4cxx

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:

Re: Using the syslog appender in log4cxx

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: >> >> appender.c

RE: Is it safe to has different processes on the same machine log to the same file?

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: Thursday, June 05, 2008 1:18 PM To: log4cxx-user@logging

Is it safe to has different processes on the same machine log to the same file?

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?

RE: Using the syslog appender in log4cxx

>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: > > > >It has already been fi

Re: Using the syslog appender in log4cxx

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

Re: Segmentation fault log4cxx 0.10.0 on app exit ( RH Linux)

On Jun 4, 2008, at 1:14 PM, GregN wrote: I made changes you recommended in src/main/cpp/objectimpl.cpp but it unfortunately didn't help. It seems that #if statement is true #if (defined(__i386__) || defined(__x86_64__)) && defined(__GNUC__) && !defined(USE_GENERAL_ATOMICS) __i386__ - defi

RE: Using the syslog appender in log4cxx

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 se