Results 1 to 6 of 6

Thread: systemd-logind fails since Tumbleweed since opensuse-20161123-0 release (boot takes 10+ minutes)

  1. #1

    Question systemd-logind fails since Tumbleweed since opensuse-20161123-0 release (boot takes 10+ minutes)

    I've been fighting with systemd-logind ever since the rolling upgrade to opensuse-20161123-0. I've not been able to find anything in the forums stating as to why this has failed or seen any reported issues. I'm only able to launch the failsafe component with XTerm in X.

    systemctl status systemd-logind:

    # systemctl status systemd-logind.service● systemd-logind.service - Login Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
    Active: failed (Result: start-limit) since Mon 2016-12-12 01:19:27 EST; 5min ago
    Docs: man:systemd-logind.service(8)
    man:logind.conf(5)
    http://www.freedesktop.org/wiki/Software/systemd/logind
    http://www.freedesktop.org/wiki/Soft...temd/multiseat
    Process: 1528 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
    Main PID: 1528 (code=exited, status=1/FAILURE)
    Status: "Shutting down..."


    Dec 12 01:19:27 xo systemd[1]: Failed to start Login Service.
    Dec 12 01:19:27 xo systemd[1]: systemd-logind.service: Unit entered failed state.
    Dec 12 01:19:27 xo systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
    Dec 12 01:19:27 xo systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
    Dec 12 01:19:27 xo systemd[1]: Stopped Login Service.
    Dec 12 01:19:27 xo systemd[1]: systemd-logind.service: Start request repeated too quickly.
    Dec 12 01:19:27 xo systemd[1]: Failed to start Login Service.
    Dec 12 01:19:27 xo systemd[1]: systemd-logind.service: Unit entered failed state.
    Dec 12 01:19:27 xo systemd[1]: systemd-logind.service: Failed with result 'start-limit'.

    release file (as of current, I've been patching in hopes this resolves the issue):

    SB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
    DISTRIB_ID="openSUSE Tumbleweed"
    DISTRIB_RELEASE="20161014"
    DISTRIB_CODENAME=""
    DISTRIB_DESCRIPTION="openSUSE Tumbleweed"
    NAME="openSUSE Tumbleweed"
    # VERSION="20161210"
    ID=opensuse
    ID_LIKE="suse"
    VERSION_ID="20161210"
    PRETTY_NAME="openSUSE Tumbleweed"
    ANSI_COLOR="0;32"
    CPE_NAME="cpe:/opensuse:tumbleweed:20161210"
    BUG_REPORT_URL="https://bugs.opensuse.org"
    HOME_URL="https://www.opensuse.org/"



    If I attempt to manually start /usr/lib/systemd/systemd-logind, I get:
    Failed to connect to system bus: No such file or directory
    Failed to fully start up daemon: No such file or directory

    I can confirm logind.conf in /etc/systemd has NOT been modified and is the original file included in the distribution.

    Result: Boot times +10 minutes, X can only run in failsafe mode.

    Other items: I've brought up the interface manually and attempted to patch up to 20161210. There is sufficient memory in the system (32 GB) and storage in the system. journalctl -xe results in the same error messages when running systemd-logind manually.

  2. #2

    Default Re: systemd-logind fails since Tumbleweed since opensuse-20161123-0 release (boot takes 10+ minutes)

    So, the saga continues.

    systemd-analyze blame results:

    1min 30.082s wickedd-auto4.service
    1min 30.082s wickedd-dhcp6.service
    1min 30.081s wickedd-dhcp4.service
    25.226s accounts-daemon.service

    # systemctl status accounts-daemon.service -l
    ● accounts-daemon.service - Accounts Service
    Loaded: loaded (/usr/lib/systemd/system/accounts-daemon.service; enabled; vendor preset: disabled)
    Active: inactive (dead) since Mon 2016-12-12 02:36:47 EST; 8min ago
    Main PID: 1556 (code=exited, status=0/SUCCESS)


    Dec 12 02:36:22 xo systemd[1]: Starting Accounts Service...
    Dec 12 02:36:47 xo accounts-daemon[1556]: error getting polkit authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
    Dec 12 02:36:47 xo accounts-daemon[1556]: Failed to initialize daemon
    Dec 12 02:36:47 xo systemd[1]: Started Accounts Service.

    So, wicked and related services are failing to start. I've attempted to re-install wicked but it still fails.

    Output from systemctl for the failed wicked* services:

    ● wicked.service loaded failed failed wicked managed network interfaces
    ● wickedd-auto4.service loaded failed failed wicked AutoIPv4 supplicant service
    ● wickedd-dhcp4.service loaded failed failed wicked DHCPv4 supplicant service
    ● wickedd-dhcp6.service loaded failed failed wicked DHCPv6 supplicant service
    ● wickedd-nanny.service loaded failed failed wicked network nanny service
    ● wickedd.service loaded failed failed wicked network management service daemon

    # systemctl status wicked.service
    ● wicked.service - wicked managed network interfaces
    Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Mon 2016-12-12 02:58:38 EST; 5min ago
    Process: 2191 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=1/FAILURE)
    Main PID: 2191 (code=exited, status=1/FAILURE)


    Dec 12 02:58:38 xo systemd[1]: Starting wicked managed network interfaces...
    Dec 12 02:58:38 xo systemd[1]: wicked.service: Main process exited, code=exited, status=1/FAILURE
    Dec 12 02:58:38 xo systemd[1]: Failed to start wicked managed network interfaces.
    Dec 12 02:58:38 xo systemd[1]: wicked.service: Unit entered failed state.
    Dec 12 02:58:38 xo systemd[1]: wicked.service: Failed with result 'exit-code'.

    # systemctl status wickedd-auto4.service
    ● wickedd-auto4.service - wicked AutoIPv4 supplicant service
    Loaded: loaded (/usr/lib/systemd/system/wickedd-auto4.service; enabled; vendor preset: disabled)
    Active: failed (Result: timeout) since Mon 2016-12-12 02:55:38 EST; 8min ago
    Process: 2178 ExecStart=/usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground (code=exited, status=0/SUCCESS)
    Main PID: 2178 (code=exited, status=0/SUCCESS)


    Dec 12 02:54:08 xo systemd[1]: Starting wicked AutoIPv4 supplicant service...
    Dec 12 02:55:38 xo systemd[1]: wickedd-auto4.service: Start operation timed out. Terminating.
    Dec 12 02:55:38 xo systemd[1]: Failed to start wicked AutoIPv4 supplicant service.
    Dec 12 02:55:38 xo systemd[1]: wickedd-auto4.service: Unit entered failed state.
    Dec 12 02:55:38 xo systemd[1]: wickedd-auto4.service: Failed with result 'timeout'.

    # systemctl status wickedd-dhcp4.service
    ● wickedd-dhcp4.service - wicked DHCPv4 supplicant service
    Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp4.service; enabled; vendor preset: disabled)
    Active: failed (Result: timeout) since Mon 2016-12-12 02:55:38 EST; 8min ago
    Process: 2176 ExecStart=/usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground (code=exited, status=0/SUCCESS)
    Main PID: 2176 (code=exited, status=0/SUCCESS)


    Dec 12 02:54:08 xo systemd[1]: Starting wicked DHCPv4 supplicant service...
    Dec 12 02:55:38 xo systemd[1]: wickedd-dhcp4.service: Start operation timed out. Terminating.
    Dec 12 02:55:38 xo systemd[1]: Failed to start wicked DHCPv4 supplicant service.
    Dec 12 02:55:38 xo systemd[1]: wickedd-dhcp4.service: Unit entered failed state.
    Dec 12 02:55:38 xo systemd[1]: wickedd-dhcp4.service: Failed with result 'timeout'.

    # systemctl status wickedd-dhcp6.service
    ● wickedd-dhcp6.service - wicked DHCPv6 supplicant service
    Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp6.service; enabled; vendor preset: disabled)
    Active: failed (Result: timeout) since Mon 2016-12-12 02:55:38 EST; 9min ago
    Process: 2177 ExecStart=/usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground (code=exited, status=0/SUCCESS)
    Main PID: 2177 (code=exited, status=0/SUCCESS)


    Dec 12 02:54:08 xo systemd[1]: Starting wicked DHCPv6 supplicant service...
    Dec 12 02:55:38 xo systemd[1]: wickedd-dhcp6.service: Start operation timed out. Terminating.
    Dec 12 02:55:38 xo systemd[1]: Failed to start wicked DHCPv6 supplicant service.
    Dec 12 02:55:38 xo systemd[1]: wickedd-dhcp6.service: Unit entered failed state.
    Dec 12 02:55:38 xo systemd[1]: wickedd-dhcp6.service: Failed with result 'timeout'.

    # systemctl status wickedd-nanny.service
    ● wickedd-nanny.service - wicked network nanny service
    Loaded: loaded (/usr/lib/systemd/system/wickedd-nanny.service; enabled; vendor preset: disabled)
    Active: failed (Result: timeout) since Mon 2016-12-12 02:58:38 EST; 6min ago
    Process: 2186 ExecStart=/usr/sbin/wickedd-nanny --systemd --foreground (code=exited, status=0/SUCCESS)
    Main PID: 2186 (code=exited, status=0/SUCCESS)


    Dec 12 02:57:08 xo systemd[1]: Starting wicked network nanny service...
    Dec 12 02:57:08 xo wickedd-nanny[2186]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds:
    Dec 12 02:57:08 xo wickedd-nanny[2186]: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files
    Dec 12 02:57:08 xo wickedd-nanny[2186]: Couldn't refresh list of active network interfaces
    Dec 12 02:58:38 xo systemd[1]: wickedd-nanny.service: Start operation timed out. Terminating.
    Dec 12 02:58:38 xo systemd[1]: Failed to start wicked network nanny service.
    Dec 12 02:58:38 xo systemd[1]: wickedd-nanny.service: Unit entered failed state.
    Dec 12 02:58:38 xo systemd[1]: wickedd-nanny.service: Failed with result 'timeout'.

    # systemctl status wickedd.service
    ● wickedd.service - wicked network management service daemon
    Loaded: loaded (/usr/lib/systemd/system/wickedd.service; indirect; vendor preset: disabled)
    Active: failed (Result: timeout) since Mon 2016-12-12 02:57:08 EST; 8min ago
    Process: 2182 ExecStart=/usr/sbin/wickedd --systemd --foreground (code=exited, status=0/SUCCESS)
    Main PID: 2182 (code=exited, status=0/SUCCESS)


    Dec 12 02:55:38 xo systemd[1]: Starting wicked network management service daemon...
    Dec 12 02:57:08 xo systemd[1]: wickedd.service: Start operation timed out. Terminating.
    Dec 12 02:57:08 xo systemd[1]: Failed to start wicked network management service daemon.
    Dec 12 02:57:08 xo systemd[1]: wickedd.service: Unit entered failed state.
    Dec 12 02:57:08 xo systemd[1]: wickedd.service: Failed with result 'timeout'.

  3. #3

    Default Re: systemd-logind fails since Tumbleweed since opensuse-20161123-0 release (boot takes 10+ minutes)

    Additional digging of /var/log/kdm.log reveals:

    Code:
    klauncher(11209) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(11203)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"
    Status of dbus.service

    Code:
    # systemctl status dbus.service -l● dbus.service - D-Bus System Message Bus
       Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
       Active: active (running) since Sun 2016-12-18 22:29:35 EST; 44min ago
         Docs: man:dbus-daemon(1)
     Main PID: 1524 (dbus-daemon)
        Tasks: 1 (limit: 512)
       CGroup: /system.slice/dbus.service
               └─1524 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    
    
    Dec 18 23:12:39 xo dbus[1524]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Dec 18 23:13:04 xo dbus[1524]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
    Dec 18 23:13:04 xo dbus[1524]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
    Dec 18 23:13:20 xo dbus[1524]: [system] Activating systemd to hand-off: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    Dec 18 23:13:45 xo dbus[1524]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
    Dec 18 23:13:45 xo dbus[1524]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
    Dec 18 23:13:45 xo dbus[1524]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
    Dec 18 23:14:10 xo dbus[1524]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out
    Dec 18 23:14:10 xo dbus[1524]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
    Dec 18 23:14:10 xo dbus[1524]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Status of dbus.socket:

    Code:
    # systemctl status dbus.socket● dbus.socket - D-Bus System Message Bus Socket
       Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static; vendor preset: disabled)
       Active: active (running) since Sun 2016-12-18 22:29:35 EST; 45min ago
       Listen: /run/dbus/system_bus_socket (Stream)
    
    
    Dec 18 22:29:35 xo systemd[1]: Listening on D-Bus System Message Bus Socket.
    I've verified dbus is running (or at least what I believe to be the minimum)

    Code:
    # systemctl status dbus.socket● dbus.socket - D-Bus System Message Bus Socket
       Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static; vendor preset: disabled)
       Active: active (running) since Sun 2016-12-18 22:29:35 EST; 45min ago
       Listen: /run/dbus/system_bus_socket (Stream)
    
    
    Dec 18 22:29:35 xo systemd[1]: Listening on D-Bus System Message Bus Socket.
    These are the dbus related packages:

    Code:
    # zypper search dbus | grep ^ii | dbus-1                              | D-Bus Message Bus System                                                          | package   
    i | dbus-1-glib                         | GLib-based library for using D-Bus                                                | package   
    i | dbus-1-glib-tool                    | Tool package for D-Bus/GLib bindings                                              | package   
    i | dbus-1-python                       | Python bindings for D-Bus                                                         | package   
    i | dbus-1-python3                      | Python bindings for D-Bus                                                         | package   
    i | dbus-1-x11                          | D-Bus Message Bus System                                                          | package   
    i | kdbusaddons-tools                   | Convenience classes for QtDBus: CLI tools                                         | package   
    i | libKF5DBusAddons5                   | Convenience classes for QtDBus                                                    | package   
    i | libQt5DBus5                         | Qt 5 DBus Library                                                                 | package   
    i | libdbus-1-3                         | Library package for D-Bus                                                         | package   
    i | libdbus-1-3-32bit                   | Library package for D-Bus                                                         | package   
    i | libdbusmenu-qt2                     | Development package for dbusmenu-qt                                               | package   
    i | libdbusmenu-qt5-2                   | Development package for dbusmenu-qt5                                              | package   
    i | libqt5-qdbus                        | Interface to Qt applications communicating over D-Bus                             | package   
    i | perl-Net-DBus                       | Perl extension for the DBus message system                                        | package   
    i | ruby2.2-rubygem-ruby-dbus           | Ruby module for interaction with D-Bus                                            | package   
    i | system-config-printer-dbus-service  | A printer administration tool -- D-Bus Service to Configure Printing              | package
    I've attempted force reinstall of dbus-1, dbus-1-glib, dbus-1-glib-tool, dbus-1-python, dbus-1-python3, and dbus-1-x11.

    Once I figure out the dbus problem, I'm fairly certain everything else that is failing will fall into place.

  4. #4
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,855
    Blog Entries
    14

    Default Re: systemd-logind fails since Tumbleweed since opensuse-20161123-0 release (boot takes 10+ minutes)

    How do you update TW?
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #5

    Default Re: systemd-logind fails since Tumbleweed since opensuse-20161123-0 release (boot takes 10+ minutes)

    Quote Originally Posted by Knurpht View Post
    How do you update TW?
    I normally run from console using:

    Code:
    zypper up

  6. #6

    Default RESOLVED: systemd-logind fails since Tumbleweed 20161123-0

    Additional debugging using strace, finally yielded the answer.

    Code:
    strace /usr/lib/systemd/systemd-logind 2>&1 | tee /tmp/systemd-logind.log
    Code:
    execve("/usr/lib/systemd/systemd-logind", ["/usr/lib/systemd/systemd-logind"], [/* 56 vars */]) = 0
    brk(NULL)                               = 0x55df6c7fb000
    mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fc4f1c3f000
    access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
    open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
    fstat(3, {st_mode=S_IFREG|0644, st_size=190186, ...}) = 0
    mmap(NULL, 190186, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc4f1c07000
    close(3)                                = 0
    [..cut for brevity..]
    open("/sys/fs/kdbus/0-system/bus", O_RDWR|O_NOCTTY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
    socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 11
    getsockopt(11, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
    setsockopt(11, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = 0
    getsockopt(11, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
    setsockopt(11, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = 0
    connect(11, {sa_family=AF_UNIX, sun_path="/var/run/dbus/system_bus_socket"}, 33) = -1 ENOENT (No such file or directory)
    close(11)                               = 0
    sendmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="PRIORITY=3\nSYSLOG_FACILITY=4\nCOD"..., iov_len=147}, {iov_base="MESSAGE=", iov_len=8}, {iov_base="Failed to connect to system bus:"..., iov_len=58}, {iov_base="\n", iov_len=1}], msg_iovlen=4, msg_controllen=0, msg_flags=0}, MSG_NO
    SIGNAL) = 214
    sendmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="PRIORITY=3\nSYSLOG_FACILITY=4\nCOD"..., iov_len=133}, {iov_base="MESSAGE=", iov_len=8}, {iov_base="Failed to fully start up daemon:"..., iov_len=58}, {iov_base="\n", iov_len=1}], msg_iovlen=4, msg_controllen=0, msg_flags=0}, MSG_NO
    SIGNAL) = 200
    epoll_ctl(4, EPOLL_CTL_DEL, 5, NULL)    = 0
    epoll_ctl(4, EPOLL_CTL_DEL, 7, NULL)    = 0
    epoll_ctl(4, EPOLL_CTL_DEL, 8, NULL)    = 0
    epoll_ctl(4, EPOLL_CTL_DEL, 10, NULL)   = 0
    epoll_ctl(4, EPOLL_CTL_DEL, 9, NULL)    = 0
    close(5)                                = 0
    close(7)                                = 0
    close(8)                                = 0
    close(10)                               = 0
    close(9)                                = 0
    close(6)                                = 0
    close(4)                                = 0
    exit_group(1)                           = ?
    +++ exited with 1 +++
    
    The bolded/italic section provided a very important clue. I built this system when TW first was released. Since dbus was looking for something in /var/run, I figured something has been updated that otherwise creates /var/run automatically on boot. I know there has been a lot of entropy regarding systemd and dbus in the past 24 calendar months.

    In /etc/fstab, I had the following line so temporary files in /var/run would be purged on system shutdown:

    Code:
    tmpfs                /var/run             tmpfs      noatime,size=1%       0 0
    
    When I compared the inode listings of /var/run and /run and noticed dbus was trying to access something in /var/run that otherwise only existed in /run, I remarked the entry in /etc/fstab.

    Now on boot /var/run is created as tmpfs and the inodes now match up (where previously connect on the socket was returning ENOENT):

    Code:
    xo:~ # ls -i /var/run/dbus/system_bus_socket
    20059 /var/run/dbus/system_bus_socket
    xo:~ # ls -i /run/dbus/system_bus_socket     
    20059 /run/dbus/system_bus_socket
    
    Summary: To resolve this issue, /var/run was remarked in /etc/fstab. System was rebooted. No additional changes were made to the system.

    System boots quickly now!

    Code:
    xo:~ # systemd-analyze blame
              1.009s apparmor.service
               969ms postfix.service
               393ms vboxdrv.service
               320ms systemd-udev-settle.service
               304ms systemd-journal-flush.service
               291ms dev-mapper-root\x2d\x2ddg\x2droot.device
               216ms ntpd.service
               184ms ModemManager.service
               182ms SuSEfirewall2.service
               176ms upower.service
               161ms SuSEfirewall2_init.service
               160ms display-manager.service
               130ms cups.service
                78ms udisks2.service
                66ms accounts-daemon.service
                66ms systemd-logind.service
                64ms systemd-fsck@dev-root\x2ddg-var.service
                64ms systemd-fsck@dev-root\x2ddg-opt.service
                63ms systemd-udev-trigger.service
                63ms systemd-fsck@dev-root\x2ddg-home.service
                62ms systemd-fsck@dev-root\x2ddg-srv.service
                62ms lvm2-activation-net.service
                56ms sshd.service
                52ms systemd-user-sessions.service
                50ms mcelog.service
                45ms NetworkManager.service
                45ms lvm2-activation-early.service
                42ms polkit.service
                42ms systemd-fsck@dev-md-boot.service
                36ms systemd-udevd.service
                30ms rpcbind.service
                28ms user@1000.service
                27ms user@0.service
                22ms lvm2-activation.service
                21ms systemd-fsck-root.service
                18ms plymouth-start.service
                18ms plymouth-read-write.service
                18ms systemd-fsck@dev-root\x2ddg-usr.service
                16ms lvm2-pvscan@9:126.service
                14ms systemd-remount-fs.service
                13ms alsa-restore.service
                12ms auditd.service
                11ms systemd-journald.service
                11ms boot-efi.mount
                11ms systemd-tmpfiles-setup-dev.service
                11ms dev-mqueue.mount
                10ms sys-kernel-debug.mount
                 9ms systemd-sysctl.service
                 9ms systemd-random-seed.service
                 9ms dev-hugepages.mount
                 9ms systemd-modules-load.service
                 8ms systemd-vconsole-setup.service
                 8ms var-lock.mount
                 6ms rc-local.service
                 6ms systemd-udev-root-symlink.service
                 6ms var-run.mount
                 5ms home.mount
                 5ms rtkit-daemon.service
                 5ms boot.mount
                 5ms opt.mount
                 5ms tmp.mount
                 5ms systemd-tmpfiles-setup.service
                 4ms mdmonitor.service
                 4ms var.mount
                 3ms srv.mount
                 3ms gpm.service
                 3ms var-tmp.mount
                 3ms kmod-static-nodes.service
                 3ms systemd-update-utmp.service
                 3ms dracut-shutdown.service
                 3ms home-ryan-.cache.mount
                 2ms systemd-update-utmp-runlevel.service
    

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •