Il 05/11/2017 20:26, Carlos E. R. ha scritto:
El 2017-11-05 a las 21:58 -0000, Marco Calistri escribió:
Il 05/11/2017 18:28, Felix Miata ha scritto:
Marco Calistri composed on 2017-11-05 12:58 (UTC-0500):
No need to guess why it takes the time it takes. Find out where the time is being spent:
systemd-analyze blame
Hi,
I was not aware of this command!
Here the result of it:
marco@linux-turion64:~> systemd-analyze blame
8.467s ModemManager.service 8.033s dev-sda5.device 7.061s initrd-switch-root.service 5.233s SuSEfirewall2_init.service 4.846s display-manager.service
5ms systemd-update-utmp-runlevel.service 5ms sys-fs-fuse-connections.mount lines 21-75/75 (END)
I think at first glance I could disable at least ModemManager and Postfix since I don't use these services and seems are taking a lot of time to start.
No, that's wrong thinking.
Instead, look at "systemd-analyze critical-chain" to see where are the actual delays. It does not really matter if a service takes half a minute if it doesn't block login, because the rest of the processes are running concurrently.
-- Cheers Carlos E. R.
(from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))
Hi Carlos, Follows further results of this issue: marco@linux-turion64:~> 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 @25.566s └─display-manager.service @23.488s +2.075s └─time-sync.target @23.485s └─ntpd.service @22.242s +1.242s └─network.target @22.173s └─NetworkManager.service @19.591s +2.581s └─SuSEfirewall2_init.service @15.517s +4.072s └─sysinit.target @15.513s └─systemd-update-utmp.service @15.476s +36ms └─systemd-tmpfiles-setup.service @14.741s +732ms └─local-fs.target @14.738s └─home.mount @14.445s +292ms └─systemd-fsck@dev-disk-by\x2did-ata\x2dSAMSUNG_HM501II_S2PMJ56B607218\x2dpart6.service @14.035s +342ms └─dev-disk-by\x2did-ata\x2dSAMSUNG_HM501II_S2PMJ56B607218\x2dpart6.device @14.034s marco@linux-turion64:~> sudo journalctl -xb --no-pager|grep SATA [sudo] password di root: nov 05 20:06:55 linux-turion64 kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x1a impl SATA mode nov 05 20:06:55 linux-turion64 kernel: ata2: SATA max UDMA/133 abar m2048@0xe8c06000 port 0xe8c06180 irq 24 nov 05 20:06:55 linux-turion64 kernel: ata4: SATA max UDMA/133 abar m2048@0xe8c06000 port 0xe8c06280 irq 24 nov 05 20:06:55 linux-turion64 kernel: ata5: SATA max UDMA/133 abar m2048@0xe8c06000 port 0xe8c06300 irq 24 nov 05 20:06:55 linux-turion64 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) nov 05 20:06:55 linux-turion64 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) nov 05 20:06:55 linux-turion64 kernel: ata5: SATA link down (SStatus 0 SControl 300) marco@linux-turion64:~> cat /etc/fstab /dev/disk/by-id/ata-SAMSUNG_HM501II_S2PMJ56B607218-part7 swap swap defaults 0 0 /dev/disk/by-id/ata-SAMSUNG_HM501II_S2PMJ56B607218-part5 / ext4 acl,user_xattr,noatime 1 1 /dev/disk/by-id/ata-SAMSUNG_HM501II_S2PMJ56B607218-part6 /home ext4 defaults,noatime 1 2 tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 (I have some doubts about correctness of parameters I used for my root partition. Regards, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171102 Kernel: 4.13.11-1.g0526da3-default - Cinnamon 3.6.0