Muitas mensagens do systemd desde a atualização para o Fedora 22

Question

Eu atualizei vários sistemas para o Fedora 22. Após a atualização, eu vejo a cada 10-20 segundos que muitas mensagens formam systemd :

Aug 27 15:30:09 host.example.org systemd[1]: Created slice user-494.slice. 
Aug 27 15:30:09 host.example.org systemd[1]: Starting user-494.slice. 
Aug 27 15:30:09 host.example.org systemd[1]: Starting User Manager for UID 494... 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Default. 
Aug 27 15:30:09 host.example.org systemd[29383]: Startup finished in 8ms. 
Aug 27 15:30:09 host.example.org systemd[1]: Started User Manager for UID 494. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Default. 
Aug 27 15:30:09 host.example.org audit[1]: <audit-1130> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@494 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 
Aug 27 15:30:09 host.example.org systemd-logind[636]: Removed session 1016. 
Aug 27 15:30:09 host.example.org systemd[1]: Stopping User Manager for UID 494... 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Default. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Default. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Shutdown. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Shutdown. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Exit the Session... 
Aug 27 15:30:09 host.example.org systemd[29383]: Received SIGRTMIN+24 from PID 29392 (kill). 
Aug 27 15:30:09 host.example.org systemd[1]: Stopped User Manager for UID 494. 
Aug 27 15:30:09 host.example.org audit[1]: <audit-1131> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@494 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 
Aug 27 15:30:09 host.example.org systemd[1]: Removed slice user-494.slice. 
Aug 27 15:30:09 host.example.org systemd[1]: Stopping user-494.slice. 

Alguma ideia do que eles poderiam ser?

    

Answer 1

No meu caso, no Debian 8, eu consegui desligar essas mensagens excessivas de systemd definindo:

em /etc/systemd/user.conf: LogLevel=notice

em /etc/systemd/system.conf: LogLevel=notice

em /etc/systemd/journald.conf: MaxLevelSyslog=notice Em seguida, aplicando as alterações: systemctl restart systemd-journald - tenha cuidado com este porque nenhuma mensagem de depuração será registrada, (ex: maillog estará praticamente vazio), muitos analisadores de log não funcionarão mais.

Para mais informações, man systemd