> Nope, I'd started using killall -USR1 httpd and then, since that rarely
> got all of them, killall -9 httpd until a ps -ax showed no httpds running. 
> We finaly bit the bullet and rebooted the web server at which point, the
> logging problems all went away but, for only one domain this time, we
> still get that Netscape "connection reset by peer" error. Tre wierd. 


Just a followup to this, the netscape errors are gone and everything seems
back to normal. It seems that while a kill -USR1 is nescesary when
changing the log files or anything like that, it also generates these
wierd Netscape errors. You have to kill it again with a kill -9 to get rid
of the Netscape problem. Very wierd. Even more annoying. Apache has a good
enough reputation for me not to just blame it on the server, but for th
elife of me I can't see what I'm doing wrong. 

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to