여러 시스템을 Fedora 22로 업그레이드했습니다. 업그레이드 후 10-20 초마다 다음과 같은 많은 메시지가 표시됩니다 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.
그들이 무엇 일 수 있는지 아십니까?
제 경우에는 Debian 8에서 다음 systemd을 설정 하여 이러한 과도한 메시지를 해제 할 수있었습니다 .
에 /etc/systemd/user.conf: LogLevel=notice
에 /etc/systemd/system.conf: LogLevel=notice
in /etc/systemd/journald.conf: MaxLevelSyslog=notice그런 다음 변경 사항을 적용합니다 systemctl restart systemd-journald.-디버그 메시지가 기록되지 않으므로 (예 : 메일 로그가 대부분 비어 있음) 많은 로그 분석기가 더 이상 작동하지 않으므로주의해야합니다.
자세한 내용은, man systemd
이 기사는 인터넷에서 수집됩니다. 재 인쇄 할 때 출처를 알려주십시오.
침해가 발생한 경우 연락 주시기 바랍니다[email protected] 삭제
몇 마디 만하겠습니다