On Sun, Nov 5, 2017 at 3:02 PM, <Francis.Montagnac@xxxxxxxx> wrote: > On Sun, 05 Nov 2017 14:33:42 -0500 Tom H wrote: >> On Sun, Nov 5, 2017 at 12:41 PM, <Francis.Montagnac@xxxxxxxx> wrote: >>> On Sun, 05 Nov 2017 12:24:15 -0500 Tom H wrote: >>>> >>>> In the networkd case, you can specify an interface >>> >>> Right but that is probably useless since: >>> >>> systemd-networkd-wait-online is a one-shot system service that waits >>> for the network to be configured. By default, it will wait for all >>> links it is aware of and which are managed by >>> systemd-networkd.service(8) to be fully configured or failed, and >>> for at least one link to gain a carrier. >> >> Why useless? Suppose that you have eth0 and eth1 and that for 50% of >> boots, eth1 is configured and up before eth0 but you want the network >> to be considered up only when eth0 is configured and up. You can then >> use "-i eth0". > > Right. I meant that in most cases one wants the network to be > considered up when all the interfaces (that should start at boot time) > are configured. You can probably set up a second (third, fourth, ...) "systemd-networkd-wait-online.service" for other interfaces. It's probably be more useful and practical if there were an option to set the interfaces that this service would use to enable "systemd-networkd-wait-online@ethX.service" _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
