Hi dears.
I suffer from this issue also. I disabled the following services:
NetworkManager-wait-online.service
avahi-daemon (service & socket)
ModemManager.service
I disabled them by âsudo systemctl disable fooâ command where âfooâ is the name of service to be disabled. However, I did not âmaskâ any of them âŚ
Does âmaskâ these service needed to get decrease in booting time ? Do I need to âmaskâ these services to gain decrease in booting time ?
And, kindly, just issuer me that if I âmaskâ any of those services, then in future I need to enabled them again, then I should do the following in sequence:
sudo systemctl unmask foo
sudo systemctl start foo
sudo systemctl enable foo
Is the above sequence correct or not ? I imagined the above sequence based upon the fact that when user need to disable service she/he perform the following:
sudo systemctl stop foo
sudo systemctl disable foo
& then after - if need to mask service - should do
sudo systemctl mask foo
Only if these services keep appearing in your systemd-analyze commands (and they do delay your boot).
If you only need to run a service once, unmask it and then start it. If you want it to run automatically, enable it as well.
Enabling the service can be done before or after starting the service, it doesnât affect running it.
Good questions. If you disable a service, it wonât automatically start at boot, but some other service or program can start it. Masking the service makes it impossible to start. If you think of disabling the service as killing it, masking it is rather like adding, ââŚand STAY dead!â
And yes, if youâve masked a service and change your mind, you have to start out by unmasking it.
Only one concern, you said:
â⌠but some other service or program can start it.â
Exactly, when this could happened, during booting process or after finishing booting process ?
It could be either. If youâve disabled a service but another service needs it, that service and still start the disabled one, or if you run a program later that needs it, it can get started. Once youâve masked it, that canât happen.
@sideburns I donât understand whatâs happening to my system
I disabled and masked ModemManager.service
Also i cleared old journal logs as @blueshurricane4 said
but this time my system took even more time than before to boot
It took about 2 min 5 sec this time
[nrj@localhost ~]$ systemd-analyze time
Startup finished in 4.201s (firmware) + 3.100s (loader) + 1.710s (kernel) + 5.996s (initrd) + 1min 50.205s (userspace) = 2min 5.214s
graphical.target reached after 1min 50.187s in userspace
Also systemd-journal-flush.service took about 31.9 seconds to complete.
Thatâs strange, unless somethingâs been writing quite a bit to your journal. The plymouth-quit-wait.service doesnât do anything except wait for boot to complete. Please post the results of
[nrj@localhost ~]$ systemd-analyze critical-chain
The time when unit became active or started is printed after the â@â character.
The time the unit took to start is printed after the â+â character.
I suggest the user should have more control over the services active upon installation or even later with a GUI tool, who in all world is still using a analogue modem connected to the PC/Laptop?
What puzzles me is that sssd.service sticks out like a sore thumb. Are you using this laptop in an enterprise setting (i.e. centralised LDAP or Active Directory login)? If not, you could probably disable sssd and shave about half a minute off of your boot. I do have to use sssd for example, but it is up in less than a second (776ms).
Itâs an HDD.
I just read about sssd.service and what I understood is that it is required when one is using his/her system as a Linux server. Please correct me if I am wrong.
As I am not using my system as a server, should I disable sssd.service also??
ModemManager handles various types of devices, among them mobile broadband modems. I find it problematic that people recommend to new users to disable a service, without knowing what it actually does.
The sssd service is System Security Services Daemon. You only really need it if your system uses external login services. My company laptop, for example, is enrolled in an (Microsoft) Active Directory domain, so in order for me to login with my company credentials, the sssd service on my laptop handles the authentication/authorisation communication with Active Directory (including Kerberos tickets, etc.).
If you only use your computer as a standalone workstation (or even as a standalone server), then you donât need sssd.
Since you indicate you have an HDD, I guess that that is the bottleneck in your startup sequence. In that case, your best bet is to disable as many startup services in the critical path towards a graphical login screen. Judging from the systemd-analyze output above, itâs already pretty minimal, except for the sssd service which you probably donât need.
Other processes (such as systemd-journal-flush.service) can be competing for disk access, slowing down the execution of the parallel chain that leads to the graphical login screen. I donât think thereâs much you can do about thatâŚ
