Network availability systemd dependency failure at boot

[Ed Greshko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/14 07:28, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> > The server with dhcp, httpd, named, and privoxy does not have NetworkManager installed. Both the WAN and the LAN ports are configured as static IPs.
>>
>> You may want to try NetworkManager and wait-online.  WAN links can take time to become active.
>
> NetworkManager does nothing for me, except to suck in another 16 packages it depends on, that I don't need. The WAN link is a statically-routed IP traffic. It's up as soon as the network interface brings up the link.

Now that you re-read what you wrote I think misunderstood WAN to be a wireless connection which would require a time to bring up the link with the AP.  If you mean WAN in the sense of a Wide Area Network, I wonder if there is a need for PPP negotiation.
 
>> I suppose the bottom line is I can't confirm your issue.  I've not made any changes to the default systemd config or service files.
>
> Neither did I, yet it broke a week or so ago. And I can now see exactly what's broken, and it was always a broken systemd configuration; except that solely by the roll of the dice, it worked until recently.
>

Well, if you know exactly what is broken and how it is broken, then I suppose it is time for bugzilla.


- -- 
If you can't laugh at yourself, others will gladly oblige.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlO4krYACgkQ4JnKjVbCBvoOnQCeJKKrYRgd+B79P68bdvC/xym2
OeoAnRrFb2/q9VDWtdzKXULo6K9NGXXD
=PSmK
-----END PGP SIGNATURE-----