Differences

This shows you the differences between two versions of the page.

--- boot:speed_up_boot [2019/11/24 20:27] – peter
+++ boot:speed_up_boot [2019/11/25 22:48] (current) – removed peter
@@ Line 1: / Line 1: @@
-====== Boot - Speed up boot ======
-===== Check which services takes most time =====
-Use the following command to check which service takes most of time
-<code bash>
-systemd-analyze blame
-</code>
-----
-===== Disabling auto-start of services during boot =====
-If you want to disable auto-starting of services during boot you can use the following command:
-<code bash>
-sudo systemctl disable some-time-eater-service.service --now
-</code>
-However, you might want to see which other services needs the service in question. To check use the following command
-<code bash>
-systemctl list-dependencies some-time-eater-service.service --reverse
-</code>
-Note: Replace some-time-eater-service.service with actual service name like postgresql@9.5-main.service.
-Note that, disabling auto-start doesn't make a service non-startable. The service can be started after boot when requirement arises. If you want to completely disable it, read the next section
-----
-===== Disabling services completely. =====
-If you want to completely disable a service so that it can't be started, you should use mask instead of disable. Like this
-<code bash>
-sudo systemctl mask <SERVICE-NAME>
-</code>
-Replace the <SERVICE-NAME> with actual name of a service
-The difference between mask and disable is mask make a service completely disable, you can't start it. You must unmask to start it with systemd (you can still start with service). But disable simply disable auto-start of a service, you can start it later.
-For example, After masking my postgresql@9.5-main.service service, when I wanted to start it with systemctl the following message is shown
-Failed to start postgresql@9.5-main.service: Unit postgresql@9.5-main.service is masked.