From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,d46468aa410c0403 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!news2.volia.net!news-out.ntli.net!newsrout1-gui.ntli.net!ntli.net!news.highwinds-media.com!newspeer1-win.ntli.net!newsfe4-win.ntli.net.POSTED!53ab2750!not-for-mail From: "Dr. Adrian Wrigley" Subject: Re: Distributed Ada, robustness etc. User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Message-Id: Newsgroups: comp.lang.ada References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: Mon, 29 May 2006 00:55:11 GMT NNTP-Posting-Host: 82.10.238.153 X-Trace: newsfe4-win.ntli.net 1148864111 82.10.238.153 (Mon, 29 May 2006 01:55:11 BST) NNTP-Posting-Date: Mon, 29 May 2006 01:55:11 BST Organization: NTL Xref: g2news2.google.com comp.lang.ada:4572 Date: 2006-05-29T00:55:11+00:00 List-Id: On Thu, 25 May 2006 01:12:08 +0000, Dr. Adrian Wrigley wrote: > > > 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