FS#50476 - [netctl] 90s boot delay because network.target and network-online.target are treated as one
Attached to Project:
Arch Linux
Opened by Liam (networkimprov) - Sunday, 21 August 2016, 18:28 GMT
Last edited by Jouke Witteveen (jouke) - Tuesday, 13 December 2016, 10:19 GMT
Opened by Liam (networkimprov) - Sunday, 21 August 2016, 18:28 GMT
Last edited by Jouke Witteveen (jouke) - Tuesday, 13 December 2016, 10:19 GMT
|
Details
Description:
Problem and workaround described here https://bbs.archlinux.org/viewtopic.php?pid=1632295#p1632295 Discussion on Arch BBS pinned blame on a systemd change, but they pin it on netctl. https://github.com/systemd/systemd/issues/4010 I have this netctl profile; the usb0 interface only appears if a usb-gadget is configured. This worked until systemd 230. Description='Usb Networking' Interface=usb0 Connection=ethernet IP=static Address=('192.168.99.2/30') |
This task depends upon
Closed by Jouke Witteveen (jouke)
Tuesday, 13 December 2016, 10:19 GMT
Reason for closing: Fixed
Additional comments about closing: e43a822
Requires systemd v233 which will be released in the beginning of 2017.
Tuesday, 13 December 2016, 10:19 GMT
Reason for closing: Fixed
Additional comments about closing: e43a822
Requires systemd v233 which will be released in the beginning of 2017.
However, note that I did include a response to this bug:
For the usb gadget, I fail to see why you would want to enable a profile when the presence of the device is not certain at boot time. Maybe you are better off with a udev rule that runs `netctl start <profile>` whenever the device is plugged in.
Before=netctl@ethernet\x2dusb.service
Wants=netctl@ethernet\x2dusb.service # netctl profile "ethernet-usb"
https://github.com/systemd/systemd/issues/4212
https://github.com/systemd/systemd/pull/4259