Re: Segmentation fault log4cxx 0.10.0 on app exit (Solaris 8)

2008-06-09 Thread Curt Arnold
On Jun 9, 2008, at 8:05 PM, Allen Liu (allliu) wrote: Hi Curt, I compiled log4cxx-0.10.0 with gcc on 3 Solaris 8/sparc workstations, 2 of which were installed with apr/apr-util 1.2.12 whereas the other apr/apr-util1.2.7. Before applying the objectimpl.cpp workaround you provided, 1. 'ma

Re: Segmentation fault log4cxx 0.10.0 on app exit (Solaris 8)

2008-06-09 Thread Allen Liu (allliu)
Hi Curt, I compiled log4cxx-0.10.0 with gcc on 3 Solaris 8/sparc workstations, 2 of which were installed with apr/apr-util 1.2.12 whereas the other apr/apr-util1.2.7. Before applying the objectimpl.cpp workaround you provided, 1. 'make check' would fail on unit-test with exit status 139 2. a

RE: Setting log file name dynamically

2008-06-09 Thread Peter Steele
We don’t use property files, only the xml config file. I tried defining my appender as but made the call setenv("LOGNAME", "tester.log", 1); in my app and tried sending a log message to this logger. The message disappeared though--no “tester.

Re: Setting log file name dynamically

2008-06-09 Thread David Schornack
Yes, there is a much easier method, at least this works very well for me. In log4j.properties, define the following ... log4j.rootLogger=info, R log4j.appender.R=org.apache.log4j.RollingFileAppender log4j.appender.R.File=../data/${logfile.name} and then in your code you simple set th

Setting log file name dynamically

2008-06-09 Thread Peter Steele
I am using the following code to set the log file dynamically instead of defining it in the xml file: DOMConfigurator::configure(config); LoggerPtr logger = Logger::getLogger(cat_name); FileAppenderPtr appender = logger->getAppender("FILE"); Pool p; a

Re: Using the syslog appender in log4cxx

2008-06-09 Thread Jacob L. Anawalt
Peter Steele wrote: I was able to get local7 to work on 0.9.7 using a simple logging test program (a.out) and the syslog appender snippet I included earlier. I added a local7 configuration line to my syslog.conf and reloaded that. Did you specify "LOCAL7" as the facility in the config file?

RE: Using the syslog appender in log4cxx

2008-06-09 Thread Peter Steele
>I was able to get local7 to work on 0.9.7 using a simple logging test program >(a.out) and the syslog appender snippet I included earlier. I added a local7 >configuration line to my syslog.conf and reloaded that. Did you specify "LOCAL7" as the facility in the config file?

Re: Using the syslog appender in log4cxx

2008-06-09 Thread Jacob L. Anawalt
Dale King wrote: On Thu, Jun 5, 2008 at 2:00 PM, Peter Steele <[EMAIL PROTECTED]> wrote: We're still stuck on 0.9.7, so this may be the motivation we need to upgrade 0.9.7 does not have the bug I described. Not sure why it wouldn't work with 0.9.7 I was able to get local7 to work on 0.9

Re: how would a wrapper for Log4cxx best look like

2008-06-09 Thread Dale King
On Mon, Jun 9, 2008 at 5:49 AM, Ning Zhao <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm trying to write a thin wrapper for log4cxx for my own application, so > that: > > 1. Instead of including log4xx-specific headers, I only need to include a > MyAppLogging.h in each cpp of my source code. In most

Log Corruption

2008-06-09 Thread Pradeep Kumar PALAPARTHY
Hi, I have a multi threaded application. There are multiple task getting created in the application which will log to a separate log file. *For each task the log file initialization happens in AbstractTaskComponent as follows:* // get the log directory File taskLogDir = TaskContr

how would a wrapper for Log4cxx best look like

2008-06-09 Thread Ning Zhao
Hi all, I'm trying to write a thin wrapper for log4cxx for my own application, so that: 1. Instead of including log4xx-specific headers, I only need to include a MyAppLogging.h in each cpp of my source code. 2. For performance's sake, I consider the " if(logger->isXEnabled())" condition