Skip to content

chroot: set exit codes to 125, 126 or 127 for errors from chroot itself #3908

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Sep 12, 2022
Merged

chroot: set exit codes to 125, 126 or 127 for errors from chroot itself #3908

merged 1 commit into from
Sep 12, 2022

Conversation

tertsdiepraam
Copy link
Member

Implements this part of the GNU docs:

   Exit status:
     125 if ‘chroot’ itself fails
     126 if COMMAND is found but cannot be invoked
     127 if COMMAND cannot be found
     the exit status of COMMAND otherwise

I think we can only reliably test the the 125 case, and not the 126 and 127 cases, but if someone has ideas about how to do that I'd be happy to add it.

@tertsdiepraam
Copy link
Member Author

CI failures seem to be unrelated

@sylvestre sylvestre merged commit 78a9f6e into uutils:main Sep 12, 2022
@niyaznigmatullin niyaznigmatullin mentioned this pull request Sep 14, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@tertsdiepraam @sylvestre