You are not logged in.
Hey everyone. So I generated a profile with wifi-menu and it seems to be hogging my startup time and preventing anything else from really happening. No login prompt until it is done. Is there a way to make the start-up of this non-blocking? Or is there a better method to get an auto-connect generally around boot time??
systemd-analyze critical-chain:
graphical.target @19.401s
└─multi-user.target @19.401s
└─getty.target @19.401s
└─getty@tty1.service @19.400s
└─systemd-user-sessions.service @19.324s +64ms
└─network.target @19.312s
└─netctl@wlo1\x2dschoene\x20Aussicht.service @6.544s +12.767s
└─sys-subsystem-net-devices-wlo1.device @6.523s
Last edited by LindyBalboa (2016-10-09 14:12:23)
Offline
The problem is that the service is “Type=oneshot” which is why it blocks until the network is started. Whilst you could create a drop-in that overrides it to be “Type=simple”, it may be better to switch to netctl-auto (even if you only have one profile) - see Automatic switching of profiles
You may also want to add the netctl hooks that start/stop network-online.target
Offline
Turning on auto switching did the trick. Would you mind explaining the significance of those hooks? By reading the wiki I could see how it might be useful in some cases, but why switch it on just because? And if so, why wouldn't that be the default?
Offline
If your system is running fine, you don't need to add the hooks - which is why I said "may". They're only needed if you have to run something that requires network access and fails if there is no access.
Offline
Okay thanks. I will leave that out for now then. Other fix works great though. Closing
Offline