[mythtv-users] frontend fails

Gary Buhrmaster gary.buhrmaster at gmail.com
Tue Feb 28 15:30:55 UTC 2017


On Tue, Feb 28, 2017 at 9:34 AM, Stephen Worthington
<stephen_agent at jsw.gen.nz> wrote:
> .... External interfaces take much longer to come up,
> and anything that gets started after only network.target will not see
> them when it starts, unless it takes a long time to start up (as it
> may if lots of software is starting up at the same time from the same
> spinning disk).

While that is true for MythTV, which iterates the interfaces
at startup, that is not generally true if the application uses
wildcard binds (which many applications default to), or the
application detects interfaces being added/removed and
updates its internal interface definitions (as applications that
do not use wildcard binds but are intended to be long
running often do).

> If you are using static IP addresses, you may still be using Network
> Manager.

And whether you are using static, or dynamic, addresses
(or interfaces) you may be alternatively be using systemd-networkd(*)(**),
which has its own systemd-networkd-wait-online.service to
be used as an After= target, and/or systemd-networkd provides
a function to wait for a specific interface to be ready if that
works best for your application
    /usr/lib/systemd/systemd-networkd-wait-online -i <interface>

There are many options, and distros have changed over time
as to which they default to (but typically maintain what you
initially chose during the original build at upgrade time), which
is why there is no one easy to follow doc that will work 100%
for everyone.




(*) Yes, while you may not have been watching, systemd
added in various networking capabilities a number of years
ago.  One platform to rule them all.

(**) Especially for desktops and servers, systemd-networkd,
has some appeal (for some) over network-manager.


More information about the mythtv-users mailing list