[mythtv-users] mythtv-backend.service should now be using Type=notify

[James Abernathy]

On Fri, Jun 14, 2024 at 9:02 AM Stephen Worthington
<stephen_agent at jsw.gen.nz> wrote:
>
> On Fri, 14 Jun 2024 08:29:56 -0400, you wrote:
>
> >>I checked my test system on Debian 12 via Linux Mint Debian Edition
> >and it did not have a Type= statement in its mythtv-backend.service. I
> >added a Type=notify statement and it still worked and viewing the
> >systemctl status I could not see any difference, but maybe a few extra
> >messages.  Nothing negative.
> >
> >JIm A
>
> Without a Type= line in a .service unit, if there is an ExecStart=
> line, the default of Type=single is used.  So you do not have to
> specify a Type value unless you want to do something different.
>
> The difference you should see with Type=notify is that if you stop
> mythbackend ("systemctl stop mythtv-backend") and then start it again
> ("systemctl start mythtv-backend"), it should take significantly
> longer before the systemctl start command finishes and returns to the
> command prompt.  That is because it will be waiting for mythbackend to
> send the "notify" event saying it has all its drives and tuners ready
> and ports open.  The extra delay is what any other program like
> mythtv-status should also see so they will not try to talk to
> mythbackend before then.  In my case where I have lots of drives and
> tuners, the delay is significant.


Thanks for the explanation.  It did take a lot longer than normal for
a systemctl restart mythtv-backend.service.

I'm going to play with it on a VM with Xubuntu 24.04 just to see.

JIm A