[mythtv-users] Fedora, ceton, systemd, and mythbackend

[Justin Moore]

Thanks everyone for the replies. My responses inline.

> Your network management software (not systemd, unless systemd-networkd
> > IS your network management software) decides when
> > network-online.target is reached.  That might be configurable.
>
> Some distros provide a "systemd-networkd-wait-online" and/or a
> "NetworkManager-wait-online" service which, if enabled, enforce
> some dependencies.  Your distro (and systemd release) will vary.
>

I'm actually using that. It uses the nm-online command, which "waits until
NetworkManager reports an active connection" (per the man page). It seems
that as soon as *something* is up, nm-online returns success. E.g., this
bug from Fedora 17 which fell off the "it's deprecated now so it looks good
to us" wagon:

https://bugzilla.redhat.com/show_bug.cgi?id=837793

Summary: nm-online returns success when either an IPv4 or IPv6 address is
assigned, but it doesn't wait for both. I ended up adding the suggestion in
the bug (and effectively Hika's suggestion), which was to add a line saying

ExecStartPost=/bin/sleep 15

which should give my DHCP server plenty of time to assign an address to my
ethernet interface. It'll obviously slow my boot time, but for this
particular system it's not a problem since it rarely reboots.

To answer Mike's comments, this ethernet interface is integrated on the
motherboard. If the post-startup sleep solution doesn't work then I'll give
the static network configuration idea a shot since my home network
shouldn't change often, ether.

Thanks,
-jdm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20150126/981c2bb8/attachment.html>