--- a/sentinel.conf
+++ b/sentinel.conf
@@ -20,21 +20,21 @@
 # The port that this sentinel instance will run on
 port 26379
 
-# By default KeyDB Sentinel does not run as a daemon. Use 'yes' if you need it.
-# Note that KeyDB will write a pid file in /var/run/keydb-sentinel.pid when
-# daemonized.
-daemonize no
-
-# When running daemonized, KeyDB Sentinel writes a pid file in
-# /var/run/keydb-sentinel.pid by default. You can specify a custom pid file
-# location here.
-pidfile /var/run/keydb-sentinel.pid
-
 # Specify the log file name. Also the empty string can be used to force
 # Sentinel to log on the standard output. Note that if you use standard
 # output for logging but daemonize, logs will be sent to /dev/null
-logfile ""
+# logfile "/var/log/keydb/sentinel.log"
 
+# To enable logging to the system logger, just set 'syslog-enabled' to yes,
+# and optionally update the other syslog parameters to suit your needs.
+syslog-enabled yes
+
+# Specify the syslog identity.
+syslog-ident sentinel
+
+# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
+# syslog-facility local0
+
 # sentinel announce-ip <ip>
 # sentinel announce-port <port>
 #
@@ -62,7 +62,7 @@
 # For KeyDB Sentinel to chdir to /tmp at startup is the simplest thing
 # for the process to don't interfere with administrative tasks such as
 # unmounting filesystems.
-dir /tmp
+dir /var/lib/keydb/sentinel
 
 # sentinel monitor <master-name> <ip> <keydb-port> <quorum>
 #
@@ -261,7 +261,7 @@
 #
 # Example:
 #
-# sentinel notification-script mymaster /var/keydb/notify.sh
+# sentinel notification-script mymaster /etc/keydb/notify.sh
 
 # CLIENTS RECONFIGURATION SCRIPT
 #
@@ -286,7 +286,7 @@
 #
 # Example:
 #
-# sentinel client-reconfig-script mymaster /var/keydb/reconfig.sh
+# sentinel client-reconfig-script mymaster /etc/keydb/reconfig.sh
 
 # SECURITY
 #