Adjust debugging MapFile doc about systemd private tmp dir #857
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When working on a Linux OS, debugging a MapFile while using the
/tmpdirectory can be misleading for people who are not aware about systemd private directory security, i.e. putting/tmp/ms_error.txtin the MapFile does not actually output the log at that exact location on your OS system. It outputs it in a private directory generated by systemd for the service used (in my case, it was Apache).So, this patch is about documenting this to avoid people that were unaware of that (like me) to fall in that trap again in the future.