From f30adac4bb359b28f2d9e1e94de2d91bbb7cecd4 Mon Sep 17 00:00:00 2001 From: Max Kellermann Date: Fri, 5 Nov 2021 06:18:28 +0100 Subject: [PATCH] doc/mpdconf.example: add comments recommending not to use log_file and pid_file --- doc/mpdconf.example | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/doc/mpdconf.example b/doc/mpdconf.example index 6f36cf8b5..9ef3b42ef 100644 --- a/doc/mpdconf.example +++ b/doc/mpdconf.example @@ -26,22 +26,25 @@ # files over an accepted protocol. # #db_file "~/.mpd/database" -# + # These settings are the locations for the daemon log files for the daemon. -# These logs are great for troubleshooting, depending on your log_level -# settings. # # The special value "syslog" makes MPD use the local syslog daemon. This # setting defaults to logging to syslog. # -#log_file "~/.mpd/log" +# If you use systemd, do not configure a log_file. With systemd, MPD +# defaults to the systemd journal, which is fine. # +#log_file "~/.mpd/log" + # This setting sets the location of the file which stores the process ID # for use of mpd --kill and some init scripts. This setting is disabled by # default and the pid file will not be stored. # -#pid_file "~/.mpd/pid" +# If you use systemd, do not configure a pid_file. # +#pid_file "~/.mpd/pid" + # This setting sets the location of the file which contains information about # most variables to get MPD back into the same general shape it was in before # it was brought down. This setting is disabled by default and the server