FS#40821 - [wpa_supplicant] Add ordering of systemd units after network-pre.target
Attached to Project:
Arch Linux
Opened by Leonid Isaev (lisaev) - Thursday, 12 June 2014, 17:53 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 20 November 2016, 19:56 GMT
Opened by Leonid Isaev (lisaev) - Thursday, 12 June 2014, 17:53 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 20 November 2016, 19:56 GMT
|
Details
Systemd-214 in [testing] introduced a new network-pre.target
which is a passive unit designed to be started before any
netrok-related services:
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
.
Can we modify wpa_supplicant-related services to be "After=network-pre.target"? This change is supposed to have zero cost on a default install, but is useful for people who actually make use of this target. Since there is an upstream update pending anyway and systemd-214 will spend some time in [testing], the above change can also be put in [testing] and moved to [core] together with, or after systemd... Thanks. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Sunday, 20 November 2016, 19:56 GMT
Reason for closing: Upstream
Sunday, 20 November 2016, 19:56 GMT
Reason for closing: Upstream
My simplistic view is (after asking all those questions on systemd-devel): before network-pre.target (if it is activated), all real interfaces are down and no virtual interfaces exist. All the configuration happens (or requested) in between network-pre and network targets.
wpa_supplicant is currently beyond this logic (it only cares about the presence of devices). Yet, it does configure the relevant interfaces (brings them up, associates, etc.). I understand that we _don't_ want to demand wpa_supplicant to be started before network.target is reached; but this request is about the "lowest ordering point" (network-pre.target), while network.target provides the "highest one".
I also don't have a bigger picture of which other daemons may need similar "fixes"...