Probably a limit you can configure with your shell. In bash it's ulimit
-c unlimited to get full core dumps and ulimit -a
to see the settings (0 bytes by default on my shell.) It and gdb might
not be helpful anyway if your log4cxx library is
stripped of debugging symbols. If you do pursue getting
in the right direction.
-Original Message-
From: Peter Steele [mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2008 5:46 PM
To: Log4CXX User
Subject: RE: File system full causes log4cxx to crash
Okay, thanks, I'll give it a try.
-Original Message-
From: Jacob L. Anawalt
Looking at FileOutputStream::write in svn head I see that if
apr_file_write
doesn't return APR_SUCCESS, it throws an IOException with the write
call's
status. I am not familar enough with the code to see who/what should
catch that,
but to work like 0.9.7 I'd expect it to be caught at some
Does not one have any comments on this? Surely someone must have
experienced this scenario, specially the volume where logs are being
recorded becoming filled up.
From: Peter Steele [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2008 11:46 AM
To: Log4CXX User
Subject: File system full
It looks like I can do this with this
make CXXFLAGS=-g -O0
By default the build uses -O2 and for gdb we need -O0. I think defining
this flag will do the trick.
From: Peter Steele [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2008 3:01 PM
To: Log4CXX User
Subject: Building
We've been getting some core dumps in our application that are appear to
be occurring in the middle of calls in the log4cxx library. We want to
build a debug version of log4cxx for our FreeBSD boxes so we can
properly analyze the core dumps with gdb. What's the trick in build a
debug version of
Peter Steele [EMAIL PROTECTED]
08/18/2008 10:35 AM
Please respond to
Log4CXX User log4cxx-user@logging.apache.org
To
Log4CXX User log4cxx-user@logging.apache.org
cc
Subject
RE: Is this a bug or user error?
A multi-file-appender would be a great addition. I
We use the DailyRollingAppender, defined as follows in our config file:
appender name=FILE
class=org.jboss.logging.appender.DailyRollingFileAppender
errorHandler
class=org.jboss.logging.util.OnlyOnceErrorHandler/
param name=File value=logfile/
param name=Append
We are using a RollingFileAppender defined as follows:
appender name=FILE class=org.apache.log4j.RollingFileAppender
param name=maxFileSize value=200MB /
param name=maxBackupIndex value=12 /
param name=File value=${LOGNAME} /
param name=Append value=false/
It would have been nice if some kind of renaming scheme was used that
was near zero-cost. For example, a date/time stamp...
-Original Message-
From: Jostein Tveit [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2008 11:42 PM
To: Log4CXX User
Subject: Re: Maximum backup index for
Does the ConversionPattern parameter support microsecond timestamps?
In Java, stdout is normally accessed using a console appender. Why are
you using this construct in the first place?
In the end it looks that we're not going to need to do this after all so
it is a moot point...
Peter
What do I need to specify in the File parameter to mean STDOUT? I have
this:
appender name=FILE class=org.apache.log4j.FileAppender
param name=File value=System.out/
...
which works in log4j but this just creates a file called System.out in
log4cxx. What's the magic formula?
Here's my un-magic invocation:
appender name=FILE class=org.apache.log4j.ConsoleAppender
Changing to ConsoleAppender isn't an option in our case unfortunately...
Thanks for the reply...
, June 11, 2008 4:09 PM
To: Log4CXX User
Subject: Re: How to set a FileAppender to STDOUT?
Peter Steele wrote:
Changing to ConsoleAppender isn't an option in our case
unfortunately...
Would you mind sharing why it's not an option? I just see the ends of
writing to
stdout and must be missing some
Any luck with this? I will post the full configuration files for syslog
and
log4cxx as well as my sample program if it might help.
No, I never did get LOCAL7 to work
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?
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;
:38 -0700, Peter Steele wrote:
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
log4cxx send log messages to the
same LOCAL7 log file that we use for our Java apps. Any suggestions on
how to accomplish this?
-Original Message-
From: Peter Steele [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2008 6:30 AM
To: Log4CXX User
Subject: RE: Using the syslog appender
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?
While this version is no longer supported by the developers, the
following
syslog appender works on my Debian systems running 0.9.7:
Thanks for the xml snippet, I'll give this a try. And we may very well
upgrade to the latest version, but we have 65+ machines with 0.9.7 so
it's a bit of a job to
23 matches
Mail list logo