0

At our university/department we run a bunch of Debian 10 labs. When people start applications from their desktop environment, some output goes to systemd journal + syslog (+ remote syslog collection) - for example "Failed to load canberra-gtk-module".

Every now and then, some application misbehaves and starts spamming stdout/stderr - possibly in an infinite loop. This fills up log filesystems both locally and on the central log host. Last time was 5.3GB of "Too many errors, abort" from COMSOL until I stopped it and had to clean up.

How can we disconnect the applications (the entire desktop session) from logging into journal+syslog? Debug output from applications started directly from the window manager are of little interest to us, if needed - they can be started from a terminal.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.