-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wpa_supplicant: systemd service directives #1
base: master
Are you sure you want to change the base?
Conversation
holomorph
commented
Jan 3, 2014
This would help obviate a lot of issues guiding new users relating to fixing the systemd unit files. |
Could you please read the top level CONTRIBUTIONS file and include Signed-hostap: tag in the commit message as described in that file? |
Please also describe why it is desirable for wpa_supplicant to exit if the interface disappears. That case can happen, e.g., with Wi-Fi USB dongles and wpa_supplicant detects when such a device is re-inserted and then continues with the existing configuration. If that is forced to exit on interface removal, this use case would be broken. |
I was not aware of that use case. I just tried what you described with a bonding interface and I agree with you. I will amend the commit. |
From 399ec17: Use correct (multi-user) target when installing systemd units [...] all services should always be installed in multi-user.target These directives (Alias, WantedBy) are documented in systemd.unit(5) Signed-hostap: Mark Oteiza <[email protected]>
Thoughts? |
Please merge this, the current units are broken. |
This is still broken, and actuallly poses real problems now... systemd upstream recommands using preset-all for enabling units which will create wrong links. there is an explicit check to avoid that in the WantedBy path |