Any other alternative to at

[Peter Silva]

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.  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;




On Sun, Feb 18, 2018 at 12:10 PM, Ralf Mardorf <silver.bullet at zoho.com> wrote:
> On Sun, 2018-02-18 at 18:07 +0100, Ralf Mardorf wrote:
>> On Sun, 2018-02-18 at 17:58 +0100, Ralf Mardorf wrote:
>
> Oops, Peng Yu wrote :D:
>> > there are different `ls`
>>
>> Now I need to be nitpicking, since there are at best common aliases for
>> "ls", non of which I ever would use, but those common aliases still are
>> using "ls". Again, depending on what you try to achieve "tree" could be
>> a good alternative for "ls". AFAIK there are _not_ different "ls" unless
>> you compare the FreeBSD "ls" of an default install with the default
>> Ubuntu install "ls", they indeed at least differ in the way you could
>> order options and paths.
>
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users