Sounds about right. From the looks of bugzilla for Apache 1.3, there are several issues with ErrorLog piping. For my purposes though, I am able to pipe the log messages through a tee first and then back out to rotatelogs. That way at least I can put a timestamp on the "Terminated"s. I'll have to check this against my Fedora box to see if it is only on the Solaris. Thanks for your reply Joe.
Wes -----Original Message----- From: Joe Orton [mailto:[EMAIL PROTECTED] Sent: Friday, July 22, 2005 6:16 AM To: Craft, Wesley Cc: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] Problem logging SIGTERM to ErrorLog when piping to rotatelogs On Thu, Jul 21, 2005 at 10:06:37AM -0400, Craft, Wesley wrote: > This is a strange problem when using rotate logs. We have multiple > apache servers running and the one without rotatelogs being piped to > from the ErrorLog directive reports the following in the error log when > shutting down: > > [Wed Jun 15 14:08:46 2005] [notice] caught SIGTERM, shutting down > > The servers that pipe the ErrorLog through rotatelogs have this (on a > line by itself, no timestamp): > > Terminated At shutdown the rotatelogs process will be sent SIGTERM along with the rest of the process group, so it may exit before the children have to to log their shutdown messages (it's a race). I don't know why it would log that line, though, might be something Solaris-specific. joe --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
