Any other alternative to at

[Chris Green]

On Sun, Feb 18, 2018 at 01:16:02PM -0500, Peter Silva wrote:
> I think 'timing' and *alternative to at* is the wrong approach.  You
> need to figure out
> how to test if the first app is *ready*, and only fire up the second
> once it is.

Exactly what I was suggesting, there are many ways to say 'have you
finished'

How to do
> so is app dependent.  If could be when a certain named pipe exists? or
> perhaps dbus,
> or check for a message in a log file.  Once you see the confirmation
> that the first component
> is running, you start the second one....
> 
> it could be a bash loop like:
> 
> while [ ! "`tail -100 /where/the/log/is | grep message`" ]; do
>     sleep 1
> done
> start_second_app;
> 

-- 
Chris Green