nohup: use POSIXLY_CORRECT to determine failure exit code #9685
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
|
GNU testsuite comparison: |
cakebaker
reviewed
Dec 18, 2025
Co-authored-by: Daniel Hofstetter <[email protected]>
|
GNU testsuite comparison: |
Contributor
Kudos, thanks! |
CrazyRoka
pushed a commit
to CrazyRoka/coreutils
that referenced
this pull request
Dec 28, 2025
* nohup: use POSIXLY_CORRECT to determine failure exit code * Update env value checking Co-authored-by: Daniel Hofstetter <[email protected]> --------- Co-authored-by: Daniel Hofstetter <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I am trying to split up this #9628 PR to make the changes easier to review.
This change just adds a helper function that reads the env variable POSIXLY_CORRECT and uses that helper function to determine the error code that is used when returning an error. There are two other bugs apart from the file permission PR that would rely on this being merged first.