On Sun, 16 Jan 2005, Ira Abramov wrote: > > Either someone changed the apache config to keep less open sockets or > > less concurrent processes, or apache, of it's own accord, came to the > > conclusion it can make do with less. You tell uswhich. > > I didn't really think Apache can make its own decisions like that, but > than I took a long look at this week's graph for "number of apache > procs" right here: > http://jenna.scso.com/hotsanic/apps/apache2.html > > since thursday morning it seems that for no apperent reason (or logic) > Apache has changed it's minservers/maxservers bahavior (though no new > binary was installed and I haven't adited the config file in 10 days > (it's dated 6 January). loads on the site are the same, as are the CPU > and netstat connections: > http://jenna.scso.com/hotsanic/netstat/connections.html > (extra listening port from wednesday is an internal service addition of > min)
question 1: could it be that you modified the config file on one date, but only reloaded/restarted the apache server on a later date? (could happen even by mistake - perhaps there's info about this in your log files, if they were not erased yet). hmm.. no further questions for now, your honor... -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
