On Monday, April 16, 2001, at 11:00 AM, <[EMAIL PROTECTED]> wrote:
> ...Paul...
> Allow me to offer another idea. What if we create temporary process for
> this case. The idea is that when we are shutting down, if processes get
> stuck with a couple of long-lived requests, then the parent checks the
> scoreboard to see how many contiguous locations there are in the
> scoreboard. It then creates a single process with that many threads.
> As
> more processes are required, we can create more temporary servers.
> Then,
> as soon as we can create a full process, we start to kill of the
> temporary
> process, and spawn new full processes.
>
> This solves your problem of having processes stuck in long-lived
> requests,
> and it solves the scoreboard issue too.
>
What about the converse? Moving the old process/threads out of the
scoreboard and into a "dying" temp area, and creating a new scoreboard
entry for the old proc/thread entries.
It seems safer (less potentially recursive, but a little slower).
Chuck Murcko
Topsail Group
http://www.topsail.org/
