Fixes for setgpio script to avoid resource busy errors #11
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
This will simply need to be run with sudo (or as root).
hlapp
added a commit
to hlapp/ninjablocks-utilities
that referenced
this pull request
Jan 18, 2016
This is posted as ninjablocks#11.
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.
This script is run every time the
/etc/init/ninjablock.confservice is started. This will generate a resource busy write error if the GPIOs have already been exported the first time. The changes fix that.Also removes the extraneous
sudoprefixes. There is no point in running this not as root, so one might as well run the whole script as sudo.