Files
termux-packages/packages/valkey/valkey.conf.patch
termux-pacman-bot 1a595682ad addpkg(main/valkey): 8.1.4
Co-authored-by: Robert Kirkman <rkirkman@termux.dev>
2025-10-12 23:34:54 +00:00

56 lines
2.3 KiB
Diff

--- a/valkey.conf
+++ b/valkey.conf
@@ -145,7 +145,7 @@ port 6379
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
# in order to get the desired effect.
-tcp-backlog 511
+tcp-backlog 127
# Unix socket.
#
@@ -351,7 +351,7 @@ tcp-keepalive 300
################################# GENERAL #####################################
# By default the server does not run as a daemon. Use 'yes' if you need it.
-# Note that the server will write a pid file in /var/run/valkey.pid when daemonized.
+# Note that the server will write a pid file in @TERMUX_PREFIX@/var/run/valkey.pid when daemonized.
# When the server is supervised by upstart or systemd, this parameter has no impact.
daemonize no
@@ -378,14 +378,14 @@ daemonize no
#
# When the server runs non daemonized, no pid file is created if none is
# specified in the configuration. When the server is daemonized, the pid file
-# is used even if not specified, defaulting to "/var/run/valkey.pid".
+# is used even if not specified, defaulting to "@TERMUX_PREFIX@/var/run/valkey.pid".
#
# Creating a pid file is best effort: if the server is not able to create it
# nothing bad happens, the server will start and run normally.
#
# Note that on modern Linux systems "/run/valkey.pid" is more conforming
# and should be used instead.
-pidfile /var/run/valkey_6379.pid
+pidfile @TERMUX_PREFIX@/var/run/valkey_6379.pid
# Specify the server verbosity level.
# This can be one of:
@@ -1208,7 +1208,7 @@ acllog-max-len 128
################################### CLIENTS ####################################
# Set the max number of connected clients at the same time. By default
-# this limit is set to 10000 clients, however if the server is not
+# this limit is set to 512 clients, however if the server is not
# able to configure the process file limit to allow for the specified limit
# the max number of allowed clients is set to the current file limit
# minus 32 (as the server reserves a few file descriptors for internal uses).
@@ -1221,7 +1221,7 @@ acllog-max-len 128
# connections, one incoming and another outgoing. It is important to size the
# limit accordingly in case of very large clusters.
#
-# maxclients 10000
+# maxclients 512
############################## MEMORY MANAGEMENT ################################