prosody: fix default logging settings#59553
Open
balejk wants to merge 1 commit intovoid-linux:masterfrom
Open
Conversation
Absolute paths to the log files need to be given to prosody as otherwise it will fail to open them on startup because it will try to create them in a directory where it has no write permissions. Also change the location of the files to be under /var/log/prosody, the previous location in /var/lib/prosody was just a corollary of using the relative paths and of prosody switching to this directory soon after startup (but not before attempting to open the log files). Also change the permissions on prosody's home directory as per the packaging instructions. Link: https://prosody.im/doc/packagers#data_directory
This file contains hidden or 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
1 participant
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.
Absolute paths to the log files need to be given to prosody as otherwise
it will fail to open them on startup because it will try to create them
in a directory where it has no write permissions.
Also change the location of the files to be under /var/log/prosody, the
previous location in /var/lib/prosody was just a corollary of using the
relative paths and of prosody switching to this directory soon after
startup (but not before attempting to open the log files).
Also change the permissions on prosody's home directory as per the
packaging instructions.
Link: https://prosody.im/doc/packagers#data_directory
Testing the changes
Local build testing