systemd-analyze 중요 체인의 출력:
multi-user.target @30.366s
└─docker.service @5.230s +851ms
└─network-online.target @5.227s
└─network.target @5.222s
└─network.service @4.872s +349ms
└─NetworkManager-wait-online.service @1.438s +3.431s
└─NetworkManager.service @1.402s +35ms
└─netcf-transaction.service @1.320s +56ms
└─basic.target @1.285s
└─sockets.target @1.285s
└─virtlockd.socket @1.285s
└─sysinit.target @1.279s
└─systemd-update-utmp.service @1.262s +16ms
└─auditd.service @1.120s +140ms
└─systemd-tmpfiles-setup.service @1.071s +44ms
└─rhel-import-state.service @1.016s +52ms
└─local-fs.target @1.011s
└─var-lib-docker-plugins.mount @5.788s
└─dev-mapper-vg1\x2droot.device @372ms +260ms
특정 항목을 빨간색으로 지정합니다. 이 경우 항목은 다음과 같습니다.
docker.service @5.230s +851ms
network.service @4.872s +349ms
NetworkManager-wait-online.service @1.438s +3.431s
NetworkManager.service @1.402s +35ms
netcf-transaction.service @1.320s +56ms
systemd-update-utmp.service @1.262s +16ms
auditd.service @1.120s +140ms
systemd-tmpfiles-setup.service @1.071s +44ms
rhel-import-state.service @1.016s +52ms
dev-mapper-vg1\x2droot.device @372ms +260ms
색상은 무엇을 나타냅니까?
답변1
+?ms빨간색은 그 뒤에 값이 있는 항목 만 강조 표시합니다 @.... systemd-analyze매뉴얼 페이지 에 따르면 :
systemd-analyze critical-chain [UNIT...] prints a tree of the
time-critical chain of units (for each of the specified UNITs or for the
default target otherwise). The time after the unit is active or started
is printed after the "@" character. The time the unit takes to start is
printed after the "+" character. Note that the output might be misleading
as the initialization of one service might depend on socket activation
and because of the parallel execution of units.
따라서 방금 충족했지만 "시작"하지 않은 단순한 목표보다는 실제 서비스(Docker, ...)와 같이 실제로 시작하는 데 시간이 걸리는 단위만 강조합니다.