Re: Distributed Ada, robustness etc.

["Dr. Adrian Wrigley" <amtw@linuxchip.demon.co.uk.uk.uk>]

On Thu, 25 May 2006 01:12:08 +0000, Dr. Adrian Wrigley wrote:

> <snip>
> 
> Hmm.  Seems to have gone quiet round here!

perhaps it's the long weekend...
(...continuing the monolog)

Anyway, it's all working nicely.  But for one small snag:

The client partitions usually complete when there are no
more active processes in the partition.  I used:

  for myclient'Termination use Local_Termination;

so that clients don't have to wait for the whole program to
terminate.  So far, so good.

But, on the rare occasions when a client call to the
"nameserver" RCI causes a new server partition to be created
(using a system call to start the code), the client
doesn't terminate until after the new partition terminates.
This is a big nuisance.

If I start the server in another terminal window, the client
terminates while the server continues.  If the nameserver
starts the server from a client call, the client waits
for the server to terminate.

I don't really understand the mechanism for this behavior,
nor how to solve it.  Does the client partition track what OS
processes need to complete before exiting? How?  The client
waits, even if the server invocation is backgrounded (with "&").
I think using the "screen" untility might help, but I couldn't get
that didn't work properly either :(
--
Adrian