[mythtv-users] Starting mythfrontend with systemd?
hobbes1069 at gmail.com
Thu Oct 5 19:40:32 UTC 2017
On Thu, Oct 5, 2017 at 1:27 PM, Bill Meek <keemllib at gmail.com> wrote:
> On 10/05/2017 01:08 PM, Alec Leamas wrote:
>> On 05/10/17 16:31, Darac Marjal wrote:
>> Yes. After mythbackend probably makes more sense than after mysql, as
>>> mythbackend probably won't come ready until it has access to the database.
>> As long as mythbackend don't have socket activation (or other systemd
>> interfaces implemented) mythbackend might very well be started in the
>> systemd sense without making a socket available.
> mythbackend --version output should help. Mine includes:
> ./configure would need to be run with the --disable-systemd_notify switch
> turn it off.
> #ifdef USING_SYSTEMD_NOTIFY
> // Provide systemd ready notification (for type=notify units)
> (void)sd_notify(0, "READY=1");
> Doesn't that 'count' as "other systemd interfaces implemented"?
If that's the case then the only thing necessary would be to change the
service type from "simple" or "forking" to "notify"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users