You could take a look at the design philosophy in
Burns, A. and Wellings, A, 2007: Concurrent and Real-Time
Programming in Ada, Cambridge Press
or
McCormick, J. W., Singhoff, F., and Hugues, J., 2011:
Building Parallel, Embedded, and Real-Time Applications
with Ada, Cambridge Press
Bruce R. Barkstrom
On Thu, Nov 7, 2013 at 8:31 PM, Jordan Padams <jordan.pad...@gmail.com>wrote:
> Hello all,
>
> I am trying to develop a pretty simple wrapper for the PushPull where I
> call the DaemonLauncher to run through the daemons in my config once and
> then shut down altogether. We currently don't have a need to have the
> software running at intervals.
>
> On that note, here are a few of the methods I've tried but haven't worked:
>
> 1. DaemonLauncher.main() - The software hangs because of the wait() waiting
> for a notify().
> 2. DaemonLauncher.viewDaemonWaitingList() - I've tried monitoring the
> daemon waiting list, and quit() the DaemonLauncher once it gets to 0, but
> then it misses the last daemon in my config.
>
> Is there a way for me to wait on the DaemonLauncher until all daemons have
> completed, then quit?
>
> I've implemented a quick workaround by creating the following method so I
> can see if daemons are still running:
>
> public boolean hasRunningDaemons() {
>
> return this.dm.hasRunningDaemons();
>
> }
> I don't have a lot of experience with daemon processes so this may just be
> something I'm blatantly missing. Appreciate the help.
>
> Thanks,
> Jordan
>
> --
> Jordan Padams
> Software Engineer
> NASA Jet Propulsion Laboratory
>
