On Thu, Apr 04, 2002 at 08:19:26PM -0800, Sung Kim wrote: > On Thu, 4 Apr 2002, Aaron Bannert wrote: > > > Can you tell us what your ScoreBoardFile directive is set to, and what > > the file permissions of that file are (if it exists) and of the parent > > directory? > I think this is a quite default. Here we are: > > # > # ScoreBoardFile: File used to store internal server process information. > # Not all architectures require this. But if yours does (you'll know because > # this file will be created when you run Apache) then you *must* ensure that > # no two invocations of Apache share the same scoreboard file. > # > <IfModule !mpm_winnt.c> > <IfModule !perchild.c> > ScoreBoardFile logs/apache_runtime_status > </IfModule> > </IfModule>
Actually this was changed recently to be commented by default. You might just be using an older config file. > > Unless you have a third-party app that needs direct access to the > > scoreboard file, you should be able to remove the ScoreBoardFile directive > > from your config. > > How can I remove the score file? Simply comment out the ScoreBoardFile line in your config. > I think the problem is that I updated one of the shared module object while apache >is running. > After this, apache wouldn't run any more. > > But if I reboot the computer, apache works file, again. This makes sense. There is no way for Apache to tell that you want to remove the old segment and start a new one. If we removed an old segment at startup we might break an already-running apache instance. The best way I see to handle this is with ipcs -m and ipcrm. -aaron
