Re: Nach Reboot resolv.conf komplett leer
von KBDCALLS- SNIPPET_DESC:
- https://debianforum.de/forum/posting.php?mode=edit&f=30&p=1189127
- SNIPPET_CREATION_TIME:
- 15.11.2018 16:49:08
- SNIPPET_PRUNE_TIME:
- Unendlich
- SNIPPET_TEXT:
-
- # systemd-analyze blame
- 25.246s NetworkManager-wait-online.service
- 21.501s networking.service
- 19.946s docker.service
- 14.213s postfix@-.service
- 9.955s minidlna.service
- 6.066s ModemManager.service
- 5.869s accounts-daemon.service
- 4.517s jenkins.service
- 4.030s vboxdrv.service
- 3.541s dev-sda3.device
- 3.515s gpm.service
- 3.038s ssh.service
- 3.013s speech-dispatcher.service
- 2.855s NetworkManager.service
- 2.761s gdomap.service
- 2.746s pppd-dns.service
- 1.900s libvirtd.service
- 1.829s polkit.service
- 1.691s lvm2-monitor.service
- 1.191s wpa_supplicant.service
- 1.078s rsyslog.service
- 1.051s keyboard-setup.service
- 848ms dev-mqueue.mount
- 847ms dev-hugepages.mount
- 846ms sys-kernel-debug.mount
- 834ms systemd-remount-fs.service
- 812ms packagekit.service
- 812ms systemd-tmpfiles-setup.service
- 792ms ebtables.service
- 717ms systemd-modules-load.service
- 694ms systemd-tmpfiles-setup-dev.service
- 669ms systemd-rfkill.service
- 621ms avahi-daemon.service
- 571ms systemd-udevd.service
- 556ms systemd-fsck@dev-disk-by\x2duuid-6f415270\x2d2b3b\x2d44a9\x2db4d5\x2d31dac2053ee3.service
- 521ms binfmt-support.service
- 518ms colord.service
- 429ms alsa-restore.service
- 428ms systemd-logind.service
- 416ms systemd-fsck@dev-disk-by\x2duuid-8a717fcf\x2d989a\x2d4add\x2da47c\x2d21f3b8f71d1e.service
- 411ms rtkit-daemon.service
- 405ms systemd-fsck@dev-disk-by\x2duuid-60162305\x2d96e7\x2d4146\x2db9dd\x2d365e759e786f.service
- 394ms systemd-journal-flush.service
- 374ms systemd-timesyncd.service
- 339ms home.mount
- 322ms upower.service
- 304ms libvirt-guests.service
- 288ms systemd-fsck@dev-disk-by\x2duuid-35fc9451\x2dd033\x2d4543\x2d98f3\x2d56663b3e9bce.service
- 285ms var.mount
- 279ms boot.mount
- 267ms console-setup.service
- 265ms vboxballoonctrl-service.service
- 264ms systemd-fsck@dev-disk-by\x2duuid-7f70a6fe\x2db4ad\x2d4e0f\x2d9b96\x2d301a62a46eaa.service
- 262ms vboxweb-service.service
- 255ms systemd-fsck@dev-disk-by\x2duuid-f05a3a08\x2d7d51\x2d44c2\x2da38c\x2ddb5fc171d2d1.service
- 246ms systemd-fsck@dev-disk-by\x2duuid-5d696abc\x2d6a82\x2d4a2c\x2da737\x2d1dc8b132c7ed.service
- 238ms systemd-random-seed.service
- 221ms vboxautostart-service.service
- 209ms proc-sys-fs-binfmt_misc.mount
- 207ms systemd-fsck@dev-disk-by\x2duuid-4ca539ae\x2d3fc4\x2d4c7a\x2dbdb9\x2da87dc30991bc.service
- 207ms systemd-fsck@dev-disk-by\x2duuid-a05ed470\x2df11b\x2d4c26\x2d9db9\x2de1e74eb3980f.service
- 206ms systemd-udev-trigger.service
- 189ms systemd-journald.service
- 156ms udisks2.service
- 154ms backups.mount
- 128ms srv.mount
- 125ms sddm.service
- 103ms postfix.service
- 101ms user@123.service
- 95ms home-proData.mount
- 87ms systemd-user-sessions.service
- 75ms systemd-update-utmp.service
- 70ms home-downloads.mount
- 69ms user@1000.service
- 61ms kmod-static-nodes.service
- 58ms systemd-sysctl.service
- 56ms dev-disk-by\x2duuid-f12ff7fa\x2d3caf\x2d4fdb\x2d8aff\x2dab0556a4dca5.swap
- 53ms home-andreas-Dokumente.mount
- 53ms home-multimedia.mount
- 6ms systemd-update-utmp-runlevel.service
- 1ms docker.socket
Quellcode
Hier kannst du den Code kopieren und ihn in deinen bevorzugten Editor einfügen. PASTEBIN_DOWNLOAD_SNIPPET_EXPLAIN