Check if root before initializing lock in create_ap and add hostapd log timestamp option #196
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If create_ap was executed without root it would initialize the /tmp/create_ap.all.lock with wrong ownership. This required the user to manually delete the lock before being able to run create_ap again.
mathiassmichno
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If
create_apwas executed without root it would initialize the/tmp/create_ap.all.lockwith wrong ownership. This required the user tomanually delete the lock before being able to run
create_apagain.Also, add
--hostapd-timestampsas option tocreate_apfor including timestamps in hostapd debug log