Package: luanti-server Version: 5.10.0+dfsg-5 Severity: normal Dear Maintainer,
When watching the luanti server logs with > journalctl -efu luanti-server I see in-game actions like > ACTION[Server]: username moves stuff to chest at (153,9,173) These lines appear thousand times per minute and clog the server logs. It is possible to put > debug_log_level = warning into /etc/luanti/default.conf, but that only affects the lines logged into /var/log/luanti/default/server.log - but the actions are still logged into syslog. The reason is that luanti-server also writes the actions to stdout/stderr, which gets sent to syslog. Source: https://forum.luanti.org/viewtopic.php?t=24713 Please find a way to keep the sysylog clean of user actions on the server. -- System Information: Debian Release: 13.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.63+deb13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages luanti-server depends on: ii libc6 2.41-12+deb13u1 ii libcurl4t64 8.14.1-2+deb13u2 ii libgcc-s1 14.2.0-19 ii libgmp10 2:6.3.0+dfsg-3 ii libjsoncpp26 1.9.6-3 ii libleveldb1d 1.23-5+b2 ii libluajit-5.1-2 2.1.0+openresty20250117-2 ii libpq5 17.7-0+deb13u1 ii libprometheus-cpp-core1.0 1.0.2-2+b3 ii libprometheus-cpp-pull1.0 1.0.2-2+b3 ii libspatialindex8 2.1.0-1 ii libsqlite3-0 3.46.1-7 ii libstdc++6 14.2.0-19 ii libzstd1 1.5.7+dfsg-1 ii luanti-data 5.10.0+dfsg-5 ii luanti-game-minetest 5.8.0.40.gc7be7c1-3 ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1 luanti-server recommends no packages. luanti-server suggests no packages. -- Configuration Files: /etc/luanti/default.conf changed: server_description = Luanti server @ dojo server_announce = false ipv6_server = true motd = Willkommen bei Luanti @ dojo. enable_pvp = false bind_address = 192.168.3.3 debug_log_level = warning -- no debconf information

