On Fri, 5 Sep 2008, Stefan Fritsch wrote: > > Am I going to run into these unspecified problems with > > reload? It's just a PHP site with a few perl CGI's and no > > mod_perl handlers. > > Uhh... Possibly. > > Some apache child processes may hang on reload. After many reloads, > you may run into the max number of apache childs or exhaust your > server's memory. > > The problem affects prefork and itk MPMs, but only if you use more > than one listening socket. If you only listen on port 80, you should > be safe.
Haha... but I am using SSL. So I am not only listening on port 80. > If you are affected, a possible workaround may be to kill all apache > child processes with "pkill -u www-data apache2" some time after the > reload. But I haven't tried this. Maybe the fix specified in the readme is not the correct fix? Perhaps removing the password from the certificate is the only guaranted fix. sux0r! Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
