On 14/10, Allyn Bottorff wrote:
Unless you use a service that actually provides it, a target will do absolutely nothing on its own. So how is using the proper things "not an ideal solution"?Systemd's own networkd should provide that target.
It shouldn't, no. It provides network.target for a reason, and then if you require something else for Internet connectivity you'll have to have your own thing provide network-online.target.
It's not an ideal solution because using that service extends the boot time
It most definitely should not delay anything that doesn't actually require network connectivity.
in a way that shouldn't be necessary in this case. It forces the boot to wait until the network is up and an IP address is assigned.
It only forces things that explicitly needs network connectivity to wait. Anything else (which is the majority of things) will not wait for that. Yay for services being started in parallel, ey.
-- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
signature.asc
Description: PGP signature
