Und ein noch gleiches testing, das bracht 2. zum login.
Jessie
Code: Alles auswählen
root@jessie:/home/michael# 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 @16.836s
└─multi-user.target @16.836s
└─exim4.service @11.117s +5.718s
└─basic.target @11.090s
└─paths.target @11.090s
└─cups.path @11.090s
└─sysinit.target @11.048s
└─nfs-common.service @10.658s +390ms
└─rpcbind.target @10.657s
└─rpcbind.service @10.337s +319ms
└─network-online.target @10.337s
└─network.target @10.337s
└─networking.service @9.743s +593ms
└─local-fs.target @9.741s
└─run-rpc_pipefs.mount @10.990s
└─local-fs-pre.target @4.971s
└─systemd-remount-fs.service @4.776s +193ms
└─keyboard-setup.service @2.862s +1.913s
└─systemd-udevd.service @2.771s +89ms
└─systemd-tmpfiles-setup-dev.service @2.251s +519ms
└─kmod-static-nodes.service @2.082s +167ms
└─system.slice @2.081s
└─-.slice @2.081s
root@jessie:/home/michael# Code: Alles auswählen
root@testing:/home/michael# 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 36.880s
└─multi-user.target @1min 36.879s
└─kdm.service @1min 35.972s +904ms
└─acpid.service @1min 35.969s
└─basic.target @1min 32.764s
└─paths.target @1min 32.762s
└─cups.path @1min 32.762s
└─sysinit.target @1min 32.352s
└─nfs-common.service @11.121s +453ms
└─rpcbind.target @11.120s
└─rpcbind.service @10.834s +285ms
└─network-online.target @10.834s
└─network.target @10.834s
└─networking.service @9.223s +1.610s
└─local-fs.target @9.221s
└─run-user-1000.mount @1min 51.103s
└─local-fs-pre.target @4.988s
└─systemd-remount-fs.service @4.961s +24ms
└─keyboard-setup.service @3.514s +1.446s
└─system.slice @2.189s
└─-.slice @2.187s
root@testing:/home/michael#
ich hätte das gerne gelöst, bin aber zu blöd.
