G'day,
I run my DB on a different machine that is slow to boot.
On a power outage my combo front/backend starts well before the DB is
available.
mythbackend is OK as it retries and I have added a test script/service
to check DB is up before starting.
Is there a simple way to start to frontend after the DB has started?
Currently the frontend is started by
~/.config/autostart/mythwelcome.desktop with
Exec=/usr/bin/mythwelcome --verbose general --loglevel info
I could add another script in there that calls mythwelcome after the DB
is up.
I could make mythwelcome start by systemd and then I could use the same
method as the backend.
Other options?
--
'ooroo
Stinga...(:)-)
---------------------------------------------------
Email:stinga+mythtv@wolf-rock.com o
You need only two tools. o /////
A hammer and duct tape. If it /@ `\ /) ~
doesn't move and it should use > (O) X< ~ Fish!!
the hammer. If it moves and `\___/' \) ~
shouldn't, use the tape. \\\
---------------------------------------------------
I run my DB on a different machine that is slow to boot.
On a power outage my combo front/backend starts well before the DB is
available.
mythbackend is OK as it retries and I have added a test script/service
to check DB is up before starting.
Is there a simple way to start to frontend after the DB has started?
Currently the frontend is started by
~/.config/autostart/mythwelcome.desktop with
Exec=/usr/bin/mythwelcome --verbose general --loglevel info
I could add another script in there that calls mythwelcome after the DB
is up.
I could make mythwelcome start by systemd and then I could use the same
method as the backend.
Other options?
--
'ooroo
Stinga...(:)-)
---------------------------------------------------
Email:stinga+mythtv@wolf-rock.com o
You need only two tools. o /////
A hammer and duct tape. If it /@ `\ /) ~
doesn't move and it should use > (O) X< ~ Fish!!
the hammer. If it moves and `\___/' \) ~
shouldn't, use the tape. \\\
---------------------------------------------------