www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: os-unixware/1082: SIGHUP causes web server to quit instead of restart (fwd)
Date Thu, 25 Sep 1997 07:20:04 GMT
The following reply was made to PR os-unixware/1082; it has been noted by GNATS.

From: Dean Gaudet <dgaudet@arctic.org>
To: apbugs@apache.org
Subject: Re: os-unixware/1082: SIGHUP causes web server to quit instead of restart (fwd)
Date: Thu, 25 Sep 1997 00:19:08 -0700 (PDT)

 
 
 
 ---------- Forwarded message ----------
 Date: Wed, 24 Sep 1997 20:50:15 -0700
 From: David Alan Pisoni <david@cnation.com>
 To: Dean Gaudet <dgaudet@arctic.org>
 Subject: Re: os-unixware/1082: SIGHUP causes web server to quit instead of restart
 
 >On Mon, 8 Sep 1997, David Alan Pisoni wrote:
 >
 >> Okay, that nailed it.  Should I but the IFDEF's back, or did both
 >>changes make the fix?
 >
 >You can put the ifdefs back probably ... the NO_SLACK thing probably fixes
 >the problem alone.  But we should try to find a better solution.  NO_SLACK
 >disables a useful feature for large webservers (lots of log files).
 >
 
 Well, I suppose I'll look forward to that in the next release! :-)  (Okay,
 I can hope...)  I don't expect it will be a problem, as I only have a few
 sites on this host.  Most of my sites are on a Linux host (which has always
 compiled Apache with 0 warnings since 1.0.  Kudos to the team on that!)
 
 >>> Also a question... on the issue of log cycling.  Is there any reason
 >>>why this sequence shouldn't work?  The following code is perl (hoping
 >>>you know perl!), and the variable $filename refers to a log file name.
 >>>This code is re run with every log file the web server creates.  Under
 >>>some conditions, I found (in earlier versions) that too many HUP's too
 >>>close together caused the server parent to die, but left many children
 >>>alive (they would continue live for awhile.  I had to individually TERM
 >>>them, then re-open the server, because they had control of the HTTP
 >>>port.  This problem went away when I put the 'sleep 5;' line in.)
 
 >
 >This bug should be fixed in 1.2.4 as well -- HUPs and such in quick
 >succession that is.
 >
 >> hmm.. linewraps make it real ugly... I'll just explain the logic.
 >>
 >> rename older files (i.e., $filename.0.gz becomes $filename.1.gz)
 >> remove oldest file
 >> if not access_log :
 >> 	rename $filename $filename.0
 >
 >I'm confused ... should access_log be $filename?  I'm still confused.  Oh
 >I think I understand you're special casing the access_log.  This should be
 >a fine method of rotating logs, assuming signal 1 is SIGHUP on your box.
 >
 >Dean
 >
 
 Ahh, it was my bad.  I looked at the script again, and saw that I was
 looking for PID in '/var/run/httpd.pid' (which is a symlink I have on
 another host of mine.)  No such symlink was there on this host.  So
 (sheepishly) oops...
 
 Thanks again for your help,
 David
 
 
 

Mime
View raw message