httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <field...@kiwi.ICS.UCI.EDU>
Subject Re: Maintaining status tables across restart
Date Wed, 01 Sep 1999 22:53:50 GMT
>I'm working on the 2nd iteration of a mod_status API with the ability
>for all modules to register status columns. One problem I'm trying to
>deal with is graceful restart. During different generations, we could
>have different modules loaded, each supplying different data. Now, I'm
>trying to allow both shared memory and pipes as implementations of the
>API, but my first implementation will be shared memory.
>For shared memory, Ken suggested that the server could maintain a list
>of scoreboards; one per generation. During a graceful restart, a new
>generation's scoreboard is created, and an old scoreboard is cleaned
>up when the last child of that generation goes away. Is this feasible?
>Any better ideas?

Why not just have a status field that indicates the child's generation?
In other words, why does the scoreboard have to change across generations
if it is shared memory and a graceful restart?


View raw message