Issue #10473 - Better warnings in jetty.sh
on filesystem permission issues
#10605
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.
Adding more checks in
jetty.sh
for common file system permission issues.Examples:
Don't have write/create access to JETTY_RUN directory path
Don't have write/create access to JETTY_PID file path location
Note: the
/var/run/
path exist in the following tests, but the Jetty user doesn't have permissions to write there.Don't have write/create access to JETTY_STATE file path location