provide an alternative path for robustlock files under QNX #1776
Conversation
This file contains hidden or 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
Signed-off-by: Ahmed Sobhy <[email protected]>
|
Build status:
|
MiguelCompany
previously approved these changes
Feb 23, 2021
MiguelCompany
approved these changes
Feb 23, 2021
MiguelCompany
added a commit
that referenced
this pull request
Feb 23, 2021
* provide an alternative path for robustlock files under QNX Signed-off-by: Ahmed Sobhy <[email protected]> * Uncrustify * Uncrustify * Uncrustify Co-authored-by: Miguel Company <[email protected]>
|
can you cherry pick to 2.0.1 as well? |
Commit 81cda6a on 2.0.x is a cherry pick of this |
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.
fixes #1766 in 2.1.x
The robust lock path is changed from /dev/shmem to /var/lock as discussed with @IkerLuengo
First we check if the directory /var/lock exists then mkdir it if it does not then proceed with the normal procedure of creating the locked file.
if PR is approved please cherry pick to 2.0.x as well, thank you.