diff --git a/wiki/install_and_setup/installation_of_ubuntu_on_raspberry_pi.md b/wiki/install_and_setup/installation_of_ubuntu_on_raspberry_pi.md index 14b12e8791abf56c870fee7843dd3c72ff7ef2ac..824c0cc22e6001e05f16f0bd877a685ca5278584 100644 --- a/wiki/install_and_setup/installation_of_ubuntu_on_raspberry_pi.md +++ b/wiki/install_and_setup/installation_of_ubuntu_on_raspberry_pi.md @@ -153,7 +153,7 @@ The answer is yes, another process is using ``dpkg`` and hence it is locked, and systemctl list-timers ``` -On the list you are like to see ``apt-daily.timer`` and ``apt-daily-upgrade.timer``. Alternatively, to check if the timers, and the services they trigger, are active, enter the following commands: +On the list you are likely to see ``apt-daily.timer`` and ``apt-daily-upgrade.timer``. Alternatively, to check if the timers, and the services they trigger, are active, enter the following commands: ``` systemctl is-active apt-daily.timer systemctl is-active apt-daily.service @@ -161,14 +161,29 @@ systemctl is-active apt-daily-upgrade.timer systemctl is-active apt-daily-upgrade.service ``` +Another way to check if the ``apt`` process is running to use ``grep`` to search the list of all processes that are running. This is done with the following command: +``` +ps aux | grep -i apt +``` +This will display a list of the processes running ``apt`` or ``apt-get``. Note that you can ignore the process containing ``grep --color=auto`` + If the services are active, then it is recommended to allow time for them to complete, and then disable the services and timers with the following commands: ``` sudo systemctl disable apt-daily.service sudo systemctl disable apt-daily.timer -sudo systemctl disable apt-daily-upgrade.timer sudo systemctl disable apt-daily-upgrade.service +sudo systemctl disable apt-daily-upgrade.timer ``` +Auto updates and upgrade settings are also specified in the file ``/etc/apt/apt.conf.d/20auto-upgrades``. Edit this file using: +``` +sudo nano /etc/apt/apt.conf.d/20auto-upgrades +``` +so that the update and upgrade options are set to a value of ``0``, i.e., the contents of the file should be: +``` +APT::Periodic::Update-Package-Lists "0"; +APT::Periodic::Unattended-Upgrade "0"; +``` ### Correct the error: ``failed to start load kernel modules``