[mythtv-users] frontend fails

[Gary Buhrmaster]

On Fri, Feb 24, 2017 at 3:07 PM, Mike Bibbings <mike.bibbings at gmail.com> wrote:

> Don.t know if a ticket has been raised, but this problem has been discussed
> in a number of threads and on mythtv forum, it is related to Systemd
> starting a whole lot of things in parallel on 16.04 systems, and
> mythtv-backend.service file not having  "wait for network... ".

Agreed, it is a packaging issue for some distributions
that were not fully systemd prepared.

One approach might be for the BE to bind to
<INADDR_ANY> rather than a specific IP (has
other implications), at least by defaull.  A perhaps
more interesting (and much much harder) approach
would be for MythTV to register itself for network
interfaces and IPs being added and removed and
dynamically add binds when addresses of "interest"
appear.

I am trying to recall the issues that were raised for
binding to <INADDR_ANY> beyond that fact that
people trying to run their BE on their network gateway
would have to be aware that they have some work(s)
to do if they want to isolate their system from the
'tubes.  [I can imagine that allowing a restriction
to only IPv4 (or only IPv6) might have value; on
the principal of least surprise I could see a default
of IPv4 only might be appropriate].