Ja, ich habe systemd, und schon überlegt den gegen upstart zu tauschen.
(Was sicherlich nicht problemlos gehen wird..)
Code:
systemd-analyze blame
1min 32.200s networking.service
8.889s dev-mapper-xsubuntu\x2d\x2dvg\x2droot.device
6.083s accounts-daemon.service
4.142s lvm2-monitor.service
3.628s polkitd.service
3.168s mdadm.service
2.850s apparmor.service
2.586s systemd-tmpfiles-setup-dev.service
2.476s keyboard-setup.service
2.387s systemd-udevd.service
1.929s systemd-modules-load.service
1.922s systemd-fsck@dev-disk-by\x2duuid-b164b9b7\x2de634\x2d4c44\x2d9f72\x2dc5154b6c8f92.service
Diesmal waren es 1.32 min..
Code:
systemd-analyze critical-chain
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.
graphical.target @1min 49.553s
└─multi-user.target @1min 49.552s
└─apport.service @1min 49.417s +131ms
└─remote-fs.target @1min 49.413s
└─remote-fs-pre.target @1min 49.412s
└─open-iscsi.service @1min 49.329s +75ms
└─iscsid.service @1min 49.245s +68ms
└─network-online.target @1min 49.242s
└─network.target @1min 49.208s
└─networking.service @17.005s +1min 32.200s
└─apparmor.service @14.110s +2.850s
└─local-fs.target @14.091s
└─var-lib-lxcfs.mount @20.265s
└─local-fs-pre.target @7.073s
└─lvm2-monitor.service @2.927s +4.142s
└─lvm2-lvmetad.service @4.589s
└─system.slice @2.891s
└─-.slice @2.860s
Bezügl. meines anderen Thread:
Den mdam dürfte ich wohl problemlos abschalten können da ich kein Raid hab?
Lesezeichen