Ensure proper file ownerships if pihole-FTL is started as root #366
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.
By submitting this pull request, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your PR:
Please submit all pull requests against the
development
branch. Failure to do so will delay or deny your requestHow familiar are you with the codebase?:
10
When started as
root
, e.g., because capabilities are not available on the current system, we drop fromroot
to some unprivileged user as soon as we did everything we needed to do asroot
(open privileged ports, etc.).Unfortunately, the log and database files were still owned by
root
in this case and hence no further logging was possible, neither to the database nor to thepihole-FTL.log
file.This PR fixes a bug discussed on Discourse.
This template was created based on the work of
udemy-dl
.