The `npt-svwaitup` program

npt-svwaitup waits for supervised services to be brought up. It works only with npt-supervise.

Interface

     npt-svwaitup timeout servicedir [ servicedir ...  ]

npt-svwaitup blocks until all the supervised services defined by the servicedirs are up. Then it exits 0.
If a hard error occurs, npt-svwaitup exits 111.
If timeout seconds elapse and npt-svwaitup is still waiting, it exits 99. A 0 value for timeout means infinite.
If npt-supervise is not running on a servicedir, npt-svwaitup considers that the service is down, and waits for npt-supervise to start and run the service.

The goal of npt-svwaitup is to provide a svwaitup implementation that does not perform active waiting.

Actually, that was the starting point of all the pipe-tools business. :-)