Mir ist augefallen das "nmbd" bim Systemstert fast 6s braucht,ist das normal?
Code
- frank@stube:~$ systemd-analyze blame
- 7.281s systemd-udev-settle.service
- 5.768s nmbd.service
- 4.389s systemd-logind.service
- 4.197s vdr.service
- 4.159s dev-sda1.device
- 2.663s systemd-journald.service
- 2.601s udisks2.service
- 2.556s x@vt7.service
- 2.410s systemd-networkd.service
- 2.121s accounts-daemon.service
- 2.025s systemd-timesyncd.service
- 2.024s systemd-resolved.service
- 1.910s snapd.service
- 1.900s networkd-dispatcher.service
- 1.533s nfs-server.service
- 1.445s avahi-daemon.service
- 1.379s proftpd.service
- 1.163s user@666.service
- 1.041s smbd.service
- 781ms systemd-rfkill.service
- 775ms apport.service
- 754ms etc-setserial.service
- 731ms grub-common.service
- 645ms keyboard-setup.service
- 633ms setserial.service
- 585ms systemd-udev-trigger.service
- 584ms user@1000.service
- 575ms alsa-restore.service
- 566ms hddtemp.service
- 552ms snapd.seeded.service
- 548ms ssh.service
- 545ms autofs.service
- 542ms wpa_supplicant.service
- 516ms nfs-mountd.service
- 487ms rsyslog.service
- 443ms lm-sensors.service
- 408ms e2scrub_reap.service
- 397ms grub-initrd-fallback.service
- 311ms atd.service
- 308ms proc-fs-nfsd.mount
- 302ms apparmor.service
- 280ms systemd-journal-flush.service
- 265ms blk-availability.service
- 224ms lvm2-monitor.service
- 219ms systemd-fsck@dev-disk-by\x2duuid-e236e91c\x2de649\x2d4c36\x2d86eb\x2d3157cce52bca.service
- 190ms plymouth-quit-wait.service
- 189ms plymouth-quit.service
- 189ms systemd-udevd.service
- 181ms polkit.service