Hello Tobias,
> 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. I understand that. > 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. My original bug report was about syslog filling with unnecessary information about users moving through the world and putting things into chests. This problem has not been addressed. I suggest adding "--quiet" as parameter which according to Luanti's help means > --quiet Print only errors to console This gives admins enough information to troubleshoot issues, while keeping the journal clean. -- Regards/Mit freundlichen Grüßen Christian Weiske -=≡ Geeking around in the name of science since 1982 ≡=-
