4 Commits

Author	SHA1	Message	Date
Jan Engelhardt	b8bde11658	doc: comma placement corrections and word order ... Set commas where there should be some. Some improvements to word order.	2014-05-07 20:13:27 -04:00
poma	7f1f9b4bcb	man: networkd typo fixes	2014-04-26 11:16:25 +02:00
Tom Gundersen	cef8b07358	networkd-wait-online: drop config file and add commandline options instead	2014-04-26 01:20:12 +02:00
Tom Gundersen	3a67e927e3	networkd-wait-online: improve interoptability and enable by default ... To make sure we don't delay boot on systems where (some) network links are managed by someone else we don't block if something else has successfully brought up a link. We will still block until all links we are aware of that are managed by networkd have been configured, but if no such links exist, and someone else have configured a link sufficiently that it has a carrier, it may be that the link is ready so we should no longer block. Note that in all likelyhood the link is not ready (no addresses/routes configured), so whatever network managment daemon configured it should provide a similar wait-online service to block network-online.target until it is ready. The aim is to block as long as we know networking is not fully configured, but no longer. This will allow systemd-networkd-wait-online.service to be enabled on any system, even if we don't know whether networkd is the main/only network manager. Even in the case networking is fully configured by networkd, the default behavior may not be sufficient: if two links need to be configured, but the first is fully configured before the second one appears we will assume the network is up. To work around that, we allow specifying specific devices to wait for before considering the network up. This unit is enabled by default, just like systemd-networkd, but will only be pulled in if anyone pulls in network-online.target.	2014-04-24 00:23:07 +02:00