aports/main/valkey/sentinel.conf.patch
2024-05-01 07:21:25 +00:00

64 lines
1.9 KiB
Diff

--- a/sentinel.conf
+++ b/sentinel.conf
@@ -9,16 +9,6 @@
# The port that this sentinel instance will run on
port 26379
-# By default Valkey Sentinel does not run as a daemon. Use 'yes' if you need it.
-# Note that Valkey will write a pid file in /var/run/valkey-sentinel.pid when
-# daemonized.
-daemonize no
-
-# When running daemonized, Valkey Sentinel writes a pid file in
-# /var/run/valkey-sentinel.pid by default. You can specify a custom pid file
-# location here.
-pidfile /var/run/valkey-sentinel.pid
-
# Specify the server verbosity level.
# This can be one of:
# debug (a lot of information, useful for development/testing)
@@ -31,14 +21,14 @@
# 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/valkey/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 no
+syslog-enabled yes
# Specify the syslog identity.
-# syslog-ident sentinel
+syslog-ident sentinel
# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
# syslog-facility local0
@@ -70,7 +60,7 @@
# For Valkey 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/valkey/sentinel
# sentinel monitor <master-name> <ip> <valkey-port> <quorum>
#
@@ -266,7 +256,7 @@
#
# Example:
#
-# sentinel notification-script mymaster /var/valkey/notify.sh
+# sentinel notification-script mymaster /etc/valkey/notify.sh
# CLIENTS RECONFIGURATION SCRIPT
#
@@ -291,7 +281,7 @@
#
# Example:
#
-# sentinel client-reconfig-script mymaster /var/valkey/reconfig.sh
+# sentinel client-reconfig-script mymaster /etc/valkey/reconfig.sh
# SECURITY
#