logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Larry Stilwell <stilw...@briarwoodfarm.com>
Subject Re: New User Question
Date Sat, 30 Apr 2005 11:36:49 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
I found the problem and it was in the code for the process.&nbsp; This is
inherited code from an acquisition last year and there are some
skeletons in the closet yet.&nbsp; Thanks for your reply.<br>
Curt Arnold wrote:<br>
<blockquote cite="mid200504301127.j3UBRp1Z014851@w204.web2010.com"
  <pre wrap="">I don't have any personal experience with this scenario and don't 
recall it being mentioned before.  Are you using or have you tried the 
SyslogAppender?  If you are using FileAppenders, my guess is that the 
open files are being closed on the parent process shutdown or child 
process start up and the child process does not try to reopen them on a 
failure.  Anybody else try this?

Could you specify whether you are using the CVS HEAD or 0.9.7 and the 
nature of your configuration?

On Apr 29, 2005, at 8:04 PM, Larry Stilwell wrote:

  <blockquote type="cite">
    <pre wrap="">I am adding log4cxx to an existing Linux process.  I get all the 
expected INFO level messages until a call to daemon() is encountered 
and all subsequent INFO messages that follow don't appear in the log.

What am I missing?

Larry Stilwell

  <pre wrap=""><!---->


View raw message