[mythtv-users] Starting mythfrontend with systemd?
Alec Leamas
leamas.alec at gmail.com
Thu Oct 5 10:39:00 UTC 2017
On 05/10/17 11:01, Darac Marjal wrote:
>
> Bah. The whole point of this was to wait for the database, wasn't it?
> Add:
> After=mysql.service
To my knowledge, mysql does not implement the proper systemd interfaces
for this to work reliably. That is, the mysql socket might be
unavailable even though the server is started - there is a window
between the two events (been there, done that).
Socket activation is really the thing here, resolving the race condition
with a missing socket. IMHO, mythbackend should implement this natively
(and mysql, but that's another list).
Not tested, but it seems that these days systemd-socket-proxyd(8) could
work as a wrapper converting a traditional server to a socket-activated
one until they implement it by themselves.
Cheers!
--alec
More information about the mythtv-users
mailing list