-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-09-02 16:53, Michael Fischer wrote:
On Fri, Sep 02, Anton Aylward wrote:
On 09/02/2016 09:05 AM, Carlos E. R. wrote:
Oh, Carlos, as I just went through this exercise this morning... be prepared for huge amounts of systemd spam in /var/log/messages.
Yes, I see that in my 13.1. I have been writing filters for lots of them for months.
See http://www.linuxquestions.org/questions/fedora-35/systemd-log-flood-session-...
as just one example I found out there. Lots of bad "just filter it" answers
out there, on that and other threads, but page two of the above seems to have figured out the appropriate workaround: `sudo loginctl enable-linger root`.
Quoting the hypothesis from the above, and trying it now:
"Systemd is running a per-user systemd for root whenever a session is started, e.g. to run a cron job. Then when root’s last session is closed, the per-user systemd is killed. The spew of log messages has to do with the the spawning and killing of that per-user systemd."
So the idea is to keep it "lingering"? Interesting trick. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlfKG/MACgkQja8UbcUWM1yc5AD/dZccBK99RwbuqahaWPPTc50v 0VG/e/PUuRCbH1CPH5gBAIYfxtqYLFZlI0PlJnmDxWJsP8/8RM94kTa9YVUlTy90 =euBq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org