On Sun, 8 Jan 2017 11:02:50 -0500 Justin Moore <justin.nonwork@xxxxxxxxx> wrote: > Just FYI, if you're trying to deal with a networking dependency > (e.g., you have multiple interfaces and you want to make sure they're > all up before proceeding) that is broken by design and has been > marked as "will not fix" by systemd, from what I can tell. System > startup will proceed as soon as *any* network interfaces are online. > If that's not your problem, then ... at least there's a chance there > might be a fix for it. No, I only have a single interface, but I notice in the logs that the wait-on-online service fails during boot. I guess it doesn't matter for my use case, or that is normal. There must be some complication on waiting for multiple interfaces that makes wait-on-online service difficult to provide, or why not just wait on *all* interfaces. My problem seems to be a timeout in a function of NetworkManager called dhcp4. When it is called, I presume it tries to allocate a dhcp address, and times out after 45 seconds when it can't. Haven't tracked it down completely. The behavior is now affecting rawhide as well, so it must have been in a recent (NetworkManager?) update, that I just applied to rawhide (I get a little behind there, since I don't run it that often). I'll probably try downloading a previous version of NetworkManager from koji, and downgrade to see if it fixes the issue. Thanks for your response. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
