Gut, dann schauen wir doch mal, ich bitte um Beurteilung der Ergebnisse. Allerdings weiss ich nicht, was "sonstige Log-Dateien" sein sollen.
- systemd-analyze blame
2.098s systemd-rfkill.service
809ms dev-sda2.device
555ms ldconfig.service
363ms systemd-journal-catalog-update.service
235ms user@1000.service
228ms systemd-journal-flush.service
224ms systemd-udev-trigger.service
200ms udisks2.service
181ms systemd-tmpfiles-setup.service
160ms systemd-tmpfiles-setup-dev.service
148ms systemd-remount-fs.service
140ms systemd-modules-load.service
132ms systemd-udevd.service
127ms modprobe@loop.service
118ms upower.service
118ms modprobe@fuse.service
117ms systemd-timesyncd.service
111ms modprobe@drm.service
103ms systemd-boot-random-seed.service
102ms modprobe@dm_mod.service
95ms systemd-vconsole-setup.service
91ms modprobe@configfs.service
89ms kmod-static-nodes.service
86ms cups.service
85ms systemd-update-utmp.service
83ms polkit.service
82ms systemd-sysusers.service
81ms dev-hugepages.mount
78ms systemd-tmpfiles-clean.service
78ms dev-mqueue.mount
75ms systemd-journald.service
73ms sys-kernel-debug.mount
70ms sys-kernel-tracing.mount
63ms systemd-zram-setup@zram0.service
61ms accounts-daemon.service
59ms systemd-sysctl.service
46ms dbus.service
46ms NetworkManager.service
45ms dev-zram0.swap
39ms systemd-update-done.service
39ms systemd-logind.service
32ms user-runtime-dir@1000.service
29ms systemd-random-seed.service
26ms boot.mount
25ms sys-fs-fuse-connections.mount
23ms systemd-user-sessions.service
17ms sys-kernel-config.mount
12ms rtkit-daemon.service
6ms tmp.mount
- systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @3.009s
└─multi-user.target @3.008s
└─cups.service @2.921s +86ms
└─network.target @2.920s
└─NetworkManager.service @2.873s +46ms
└─dbus.service @2.800s +46ms
└─basic.target @2.766s
└─sockets.target @2.766s
└─dbus.socket @2.766s
└─sysinit.target @2.761s
└─systemd-vconsole-setup.service @3.711s +95ms
└─systemd-journald.socket @997ms
└─system.slice @940ms
└─-.slice @940ms
Das Aktivieren der Netzwerkverbindung dauerte in diesem, wie in jedem Fall wie oben im ersten Beitrag beschrieben, so lange.