Bug#1125461: marked as pending in luanti

[Tobias Frost]

Hallo Christian,

On Sat, 14 Feb 2026 19:42:06 +0100 Christian Weiske 
> 
> This will not fix the problem that user actions are filling up
> syslog/journald.
> 
> You're merely removing the separate log file, which is the only thing
> that could be influenced by the "debug_log_level" setting.
> 
> The user actions sent to stdout/stderr are still logged to journald.
> 
> I think the right solution would be to only log to the separate log
> file, and not to journald (by piping output to /dev/null)

Using journald has many advantages for users and administrators, and
from a Debian packaging point of view it is the right default. Ditching
journald in favour of s log file would be a step backwards.

journald provides structured, centralized logging for all services. It
allows filtering by unit, priority, time range, boot, etc. via
journalctl, without each package having to implement its own log
management. It also handles log rotation, retention limits, and rate
limiting centrally, which helps prevent uncontrolled disk usage. In
setups with multiple instances (e.g. when started via luanti-
server at .service), journald automatically keeps logs separated per unit,
which is much cleaner than juggling multiple per-instance log files.

Piping stdout/stderr to /dev/null would hide warnings and errors from
administrators and make troubleshooting harder. The default behaviour
of services logging to stdout/stderr and letting systemd capture that
output is intentional and consistent with how other daemons in Debian
are packaged.

If a local administrator prefers a different setup, this can be
adjusted via systemd drop-in overrides.

--
tobi