> > > For the time being, the shared storage will still be allocated in a "big
> > > chunk" up front (until we can figure out how to allocate and free smaller
> > > chunks). We will unfortunately still be allocating more than is usually
> > > needed, but will now be able to avoid allocating the (bigger) part related
> > > to mod_status if it isn't loaded. So overall it should usually be a
> > > memory savings.
> > >
> >
> > Seems to me, this will break gracefull restarts if you're adding
> > mod_status at that time, since the scoreboard is allocated at initial
> > boot and not at restarts.
>
> [EMAIL PROTECTED] wrote:
> > How does that work if mod_status is later enabled by modifying the config
> > file? Won't it all of a sudden break?
>
> Yes, restarts would be problematic for the time being. This means that we
> either don't save the memory for now, or we save memory but don't allow
> mod_status to be added in during a restart.
>
> I hope that in the long run we will find a shared memory solution to this
> problem so that we can allocate chunks of shared memory later if required.
You can't break graceful restarts with this change. The problem is that
adding mod_status using a graceful restart is actually a common occurance.
People do that because they are having problems with the server, and they
want to monitor it, but they don't want to kick people off the server.
Until the shared memory problem is solved, I am -1 for this change.
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
