--- Comment #6 from ---
Probably, we do a lot of active restarts both to bring in managed changes to
the configuration (but only hourly) and reactive restarts when apache stops
responding.  I will examine and get back to you. 

My feeling after reading the code is that an old process still hasn't detached
from the SHM segment, so the SHM key hangs around, but the placeholder file
does get deleted, so when the next Apache process comes along, presumably
without a filled-in global list, it attempts to re-instate a SHM key that still
hasn't been quite released by the last process.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to