• reduce boot time

    any ideas on how to reduce userspace in boot time

    Startup finished in 4.033s (kernel) + 28.284s (userspace) = 32.317s
    graphical.target reached after 28.284s in userspace


  • systemd-analyze blame
  • hey thanks for help i got this back after the command

         12.858s systemd-journal-flush.service
         10.280s lvm2-monitor.service
          9.903s mariadb.service
          8.676s dev-sda2.device
          5.190s ModemManager.service
          2.876s NetworkManager.service
          2.441s systemd-udevd.service
          2.412s polkit.service
          2.158s systemd-logind.service
          2.151s avahi-daemon.service
          2.070s accounts-daemon.service
          1.607s systemd-rfkill.service
          1.592s ldconfig.service
          1.185s systemd-sysusers.service
           988ms systemd-modules-load.service
           951ms wpa_supplicant.service
           920ms udisks2.service
           896ms upower.service
           853ms systemd-tmpfiles-setup-dev.service
           716ms [email protected]
           674ms gdm.service
           586ms org.cups.cupsd.service
           562ms sys-kernel-debug.mount
           487ms boot.mount
           451ms systemd-journal-catalog-update.service
           413ms dev-mqueue.mount
           409ms colord.service
           339ms systemd-timesyncd.service
           329ms dev-disk-by\x2duuid-00cacf12\x2dd1d0\x2d44dc\x2da136\x2d3ff31>
           302ms kmod-static-nodes.service
           290ms systemd-random-seed.service
           272ms systemd-remount-fs.service
           271ms dev-hugepages.mount
           251ms systemd-tmpfiles-setup.service
           236ms systemd-udev-trigger.service
           198ms systemd-user-sessions.service
           194ms systemd-journald.service
           176ms bluetooth.service
           161ms [email protected]:intel_backlight.service
           111ms systemd-update-done.service
            95ms systemd-sysctl.service
            63ms systemd-update-utmp.service
  • you can see the longest 3:

    12.858s systemd-journal-flush.service
        10.280s lvm2-monitor.service
         9.903s mariadb.service

    lvm2-monitor.service can be diosabled if i am not wrong if you do not use (and not will in future ) LVM…

    mariadb.service is may needed for something…

    and 12.858s for systemd-journal-flush.service is unusual…

    systemd-analyze critical-chain

    is also a good one to see what is causing the lag…

  • ok sorry but i don’t know how to disable these services from startup can you help me out?

    graphical.target @29.459s
    └─multi-user.target @29.459s
    └─mariadb.service @19.555s +9.903s
    └─network.target @19.550s
    └─wpa_supplicant.service @21.680s +951ms
    └─basic.target @16.669s
    └─sockets.target @16.669s
    └─dbus.socket @16.669s
    └─sysinit.target @16.628s
    └─systemd-timesyncd.service @16.289s +339ms
    └─systemd-tmpfiles-setup.service @15.976s +251ms
    └─systemd-journal-flush.service @3.117s +12.858s
    └─systemd-remount-fs.service @2.842s +272ms
    └─systemd-journald.socket @2.549s
    └─system.slice @2.257s
    └─-.slice @2.257s

  • Thank you for the help i solved the issue by disabling a few services and clearing the log from from the journal /var/log/journal

  • du /var/log/Journal -h

  • Sorry and i can not edit

    du /var/log/journal -h

  • journalctl --disk-usage
    Archived and active journals take up 1008.1M in the file system.

    The config file for the journalctl lies under /etc/systemd/journald.conf

    set SystemMaxUse to something you can live with:

  • [[email protected] ~]$ sudo paccache -d
    ==> no candidate packages found for pruning
    [[email protected] ~]$
  • sudo /usr/bin/mandb

  • ⏫ and reboot

  • du /var/cache/pacman/ -h

    can be a shocking number after some years… as it will not be cleaned up…

boot320 Posts 13Views 733
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.