Hi, are you sure it’s the best solution? why all those log files when there was no problem up until the previous release? with many computers and many users the load goes up a lot and you have lots of useless logs. Mine wants to be a constructive and not offensive criticism, it seems to me that you have made some mistakes. I don’t seem to be the only one to report these problems. Greetings.
In all likelihood this wasn’t a a deliberate change on the part of the Univention team. Instead, it was likely a change introduced by newer versions of systemd or logind itself.
Sure, you’re not the only one reporting this as those messages occur for everyone runing a recent version of UCS. However, most people simply ignore those messages, as do I. The impact those messages have is negligible; they only occur each time a user opens a new connection that actually opens a system session, and that simply doesn’t happen all that often that it could induce high system load.
If the log file growth is something you’re worrying about, there are settings that control the maximum size of the journal; see man journald.conf (on UCS systems the journald.conf file is managed by UCR templates; see ucr search journal for the corresponding variables you can change). You don’t even have to worry about the journal filling up your file system as the journal daemon dosen’t just have a maximum journal size setting, it also has a setting for how much space it will leave at least on the file system (setting SystemKeepFree).
Additionally you can filter those messages as I’ve pointed out already.
This really isn’t a bug. It’s normal system behavior. That behavior has changed recently, sure, but software behavior changes all the time.