[systemd] Use a private /tmp directory #112372
Merged
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.
This creates an isolated tmp directory for the kibana service. Reads
and writes to /tmp will end up in
/tmp/systemd-private-*-kibana.service-*/tmp
,isolated to the current process.
Reference: https://www.freedesktop.org/software/systemd/man/systemd.exec.html#PrivateTmp=
In practice, after #112198 I believe the only remaining use of os.tmpdir() in production is by the legacy log rotation feature.
I tested access by setting:
I tailed logs until setup was done and there were no errors: