Keresés

Új hozzászólás Aktív témák

  • petya220

    senior tag

    válasz petya220 #30815 üzenetére

    Ubuntu 16.04 64bit

    sudo systemd-analyze blame

    petya230@petya230-ThinkPad-R61:~$ sudo systemd-analyze blame
    11.272s networking.service
    10.726s lightdm.service
    10.680s plymouth-quit-wait.service
    10.331s plymouth-read-write.service
    1.344s dev-sda1.device
    381ms accounts-daemon.service
    377ms console-setup.service
    368ms apparmor.service
    275ms ModemManager.service
    267ms apport.service
    266ms ondemand.service
    264ms irqbalance.service
    245ms grub-common.service
    243ms speech-dispatcher.service
    215ms keyboard-setup.service
    205ms NetworkManager.service
    202ms alsa-restore.service
    187ms systemd-logind.service
    181ms systemd-journald.service
    178ms systemd-udev-trigger.service
    170ms gpu-manager.service
    146ms systemd-rfkill.service
    145ms upower.service
    lines 1-23...skipping...
    11.272s networking.service
    10.726s lightdm.service
    10.680s plymouth-quit-wait.service
    10.331s plymouth-read-write.service
    1.344s dev-sda1.device
    381ms accounts-daemon.service
    377ms console-setup.service
    368ms apparmor.service
    275ms ModemManager.service
    267ms apport.service
    266ms ondemand.service
    264ms irqbalance.service
    245ms grub-common.service
    243ms speech-dispatcher.service
    215ms keyboard-setup.service
    205ms NetworkManager.service
    202ms alsa-restore.service
    187ms systemd-logind.service
    181ms systemd-journald.service
    178ms systemd-udev-trigger.service
    170ms gpu-manager.service
    146ms systemd-rfkill.service
    145ms upower.service
    141ms pppd-dns.service
    140ms rsyslog.service
    119ms systemd-udevd.service
    103ms avahi-daemon.service
    102ms snapd.autoimport.service
    94ms thermald.service
    73ms systemd-user-sessions.service
    72ms systemd-modules-load.service
    67ms polkitd.service
    67ms systemd-journal-flush.service
    64ms systemd-tmpfiles-setup-dev.service
    62ms systemd-tmpfiles-setup.service
    51ms plymouth-start.service
    50ms systemd-update-utmp.service
    43ms user@1000.service
    42ms systemd-timesyncd.service
    42ms bluetooth.service
    38ms ssh.service
    31ms dns-clean.service
    30ms user@108.service
    28ms colord.service
    24ms sys-kernel-debug.mount
    24ms dev-hugepages.mount
    23ms systemd-remount-fs.service
    22ms systemd-random-seed.service
    22ms dev-mqueue.mount
    21ms rc-local.service
    16ms kmod-static-nodes.service
    15ms wpa_supplicant.service
    15ms resolvconf.service
    13ms ufw.service
    13ms dev-disk-by\x2duuid-ee9d9182\x2d8252\x2d49b0\x2d84e4\x2dd26626fa5b5c.swap
    10ms systemd-sysctl.service
    6ms sys-fs-fuse-connections.mount
    5ms systemd-update-utmp-runlevel.service
    5ms rtkit-daemon.service
    5ms ureadahead-stop.service
    4ms systemd-backlight@backlight:acpi_video0.service
    4ms setvtrgb.service
    2ms systemd-backlight@backlight:intel_backlight.service
    1ms snapd.socket
    lines 12-64/64 (END)

    sudo systemd-analyze critical-chain

    petya230@petya230-ThinkPad-R61:~$ sudo 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 @22.905s
    └─lightdm.service @12.173s +10.726s
    └─systemd-user-sessions.service @11.942s +73ms
    └─basic.target @11.806s
    └─sockets.target @11.806s
    └─snapd.socket @11.804s +1ms
    └─sysinit.target @11.803s
    └─swap.target @1.491s
    └─dev-disk-by\x2duuid-ee9d9182\x2d8252\x2d49b0\x2d84e4\x2dd26626fa5b5c.swap @1.476s +13ms
    └─dev-disk-by\x2duuid-ee9d9182\x2d8252\x2d49b0\x2d84e4\x2dd26626fa5b5c.device @1.475s

    Ebből azt veszem ki, hogy a grafikus részben van a gond... :D

Új hozzászólás Aktív témák

Hirdetés