Do I really need apt-daily.service and apt-daily-upgrade.service?Slow Boot time apt-daily-upgrade.service and...
Midterm in Mathematics Courses
Single-row INSERT...SELECT much slower than separate SELECT
Plausible reason to leave the Solar System?
How much mayhem could I cause as a fish?
Why does 0.-5 evaluate to -5?
Taking headphones when quitting job
Does the ditching switch allow an A320 to float indefinitely?
Coworker asking me to not bring cakes due to self control issue. What should I do?
Plausible reason for gold-digging ant
Will rerolling initiative each round stop meta-gaming about initiative?
What can I do to encourage my players to use their consumables?
"Starve to death" Vs. "Starve to the point of death"
Why did Luke use his left hand to shoot?
Is a creature that sees a Medusa's eyes automatically subjected to a saving throw?
What's the oldest plausible frozen specimen for a Jurassic Park style story-line?
A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?
How to write cases in LaTeX?
Crack the bank account's password!
Why is 'diphthong' pronounced the way it is?
Critique vs nitpicking
Article. The word "Respect"
Custom shape shows unwanted extra line
Need help with a circuit diagram where the motor does not seem to have any connection to ground. Error with diagram? Or am i missing something?
Subsurf on a crown. How can I smooth some edges and keep others sharp?
Do I really need apt-daily.service and apt-daily-upgrade.service?
Slow Boot time apt-daily-upgrade.service and apt-daily.service on Xubuntu 18.04 - ASUS K70IO laptopUbuntu 16.04 slow boot (apt-daily.service)Package operation failed E: Sub-process /usr/bin/dpkg returned an error code (1)how to configure `aptd` to really stop accessing the internet when the machine starts?Ubuntu 15.04 very slow bootUbuntu 15.10 takes long time to bootHigh boottime - Big gaps in dmesgSlow boot time on ubuntu 17.10(3mins +)Some services causes slower boot time Ubuntu 17.10Ubuntu 18.04 LTS booting very slow after recent updateVery slow load on Ubuntu 18.04Ubuntu 18.04 on Asus Vivobook S take extra long to boot?Ubuntu 18.04 is taking long to loadboot startup speedup Ubuntu 18.04
The startup with 18.04 seems to take a bit longer than 17.10 so I ran systemd-analyze blame and found that apt-daily.service and apt-daily-upgrade.service are taking up over three minutes between them.
:~$ systemd-analyze time
Startup finished in 9.173s (kernel) + 3min 30.201s (userspace) = 3min 39.375s
graphical.target reached after 15.268s in userspace
:~$ systemd-analyze blame
1min 52.265s apt-daily-upgrade.service
1min 27.579s apt-daily.service
6.603s NetworkManager-wait-online.service
5.105s plymouth-quit-wait.service
1.517s plymouth-start.service
1.439s dev-sda1.device.............
So, what are these services actually doing (checking apt is up to date I imagine), why do they take so long and do I really need them to run on every bootup?
boot apt
edited May 22 '18 at 6:41
muru
1
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
add a comment |
The startup with 18.04 seems to take a bit longer than 17.10 so I ran systemd-analyze blame and found that apt-daily.service and apt-daily-upgrade.service are taking up over three minutes between them.
:~$ systemd-analyze time
Startup finished in 9.173s (kernel) + 3min 30.201s (userspace) = 3min 39.375s
graphical.target reached after 15.268s in userspace
:~$ systemd-analyze blame
1min 52.265s apt-daily-upgrade.service
1min 27.579s apt-daily.service
6.603s NetworkManager-wait-online.service
5.105s plymouth-quit-wait.service
1.517s plymouth-start.service
1.439s dev-sda1.device.............
So, what are these services actually doing (checking apt is up to date I imagine), why do they take so long and do I really need them to run on every bootup?
boot apt
edited May 22 '18 at 6:41
muru
1
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
1
See Debian Bug #844453 for a complete explanation of the issue, and current work in progress to fix.
– user535733
May 22 '18 at 11:48
add a comment |
The startup with 18.04 seems to take a bit longer than 17.10 so I ran systemd-analyze blame and found that apt-daily.service and apt-daily-upgrade.service are taking up over three minutes between them.
:~$ systemd-analyze time
Startup finished in 9.173s (kernel) + 3min 30.201s (userspace) = 3min 39.375s
graphical.target reached after 15.268s in userspace
:~$ systemd-analyze blame
1min 52.265s apt-daily-upgrade.service
1min 27.579s apt-daily.service
6.603s NetworkManager-wait-online.service
5.105s plymouth-quit-wait.service
1.517s plymouth-start.service
1.439s dev-sda1.device.............
So, what are these services actually doing (checking apt is up to date I imagine), why do they take so long and do I really need them to run on every bootup?
boot apt
edited May 22 '18 at 6:41
muru
1
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
The startup with 18.04 seems to take a bit longer than 17.10 so I ran systemd-analyze blame and found that apt-daily.service and apt-daily-upgrade.service are taking up over three minutes between them.
:~$ systemd-analyze time
Startup finished in 9.173s (kernel) + 3min 30.201s (userspace) = 3min 39.375s
graphical.target reached after 15.268s in userspace
:~$ systemd-analyze blame
1min 52.265s apt-daily-upgrade.service
1min 27.579s apt-daily.service
6.603s NetworkManager-wait-online.service
5.105s plymouth-quit-wait.service
1.517s plymouth-start.service
1.439s dev-sda1.device.............
So, what are these services actually doing (checking apt is up to date I imagine), why do they take so long and do I really need them to run on every bootup?
boot apt
boot apt
edited May 22 '18 at 6:41
muru
1
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
edited May 22 '18 at 6:41
muru
1
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
edited May 22 '18 at 6:41
muru
1
edited May 22 '18 at 6:41
muru
1
edited May 22 '18 at 6:41
muru
1
1
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
asked May 22 '18 at 6:33
SteveInBavariaSteveInBavaria
574419
574419
1
See Debian Bug #844453 for a complete explanation of the issue, and current work in progress to fix.
– user535733
May 22 '18 at 11:48
add a comment |
1
See Debian Bug #844453 for a complete explanation of the issue, and current work in progress to fix.
– user535733
May 22 '18 at 11:48
1
1
See Debian Bug #844453 for a complete explanation of the issue, and current work in progress to fix.
– user535733
May 22 '18 at 11:48
See Debian Bug #844453 for a complete explanation of the issue, and current work in progress to fix.
– user535733
May 22 '18 at 11:48
add a comment |
3 Answers
3
active
oldest
votes
You can decide it by yourself. But on my systems (mainly 16.04 LTS) I have disabled both with:
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
Because of the fact that some functionality on desktop is provided by update-manager and
I do not want to get error messages about lock-files in archives or lists directories whenever I run apt manually.
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
add a comment |
Yes, it is important, you need it.
If spending internet data is a concern to you like it is to me, you may not want it to be started so often.
But that is useful to keep your OS secure by keeping packages updated.
Now about the slow startup, others already answered how to workaround that :)
add a comment |
You can change the timer of the service, it should run after the boot, actually.
Here's the solution.
Ubuntu 16.04 slow boot (apt-daily.service)
As a workaround, do sudo systemctl edit apt-daily.timer and paste the following text into the editor window:
# apt-daily timer configuration override
[Timer]
OnBootSec=15min
OnUnitActiveSec=1d
AccuracySec=1h
RandomizedDelaySec=30min
This changes the "timer" that triggers apt-daily.service to run at a random time between 15 min and 45 min after boot, and once a day thereafter. See the systemd.timer manpage for additional (not very well written, alas) explanation of what this means.
If this is not working, create/edit the file in /etc/systemd/system/apt-daily.timer
edited 6 hours ago
gman
1,07331531
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
add a comment |
protected by N0rbert Dec 23 '18 at 16:29
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can decide it by yourself. But on my systems (mainly 16.04 LTS) I have disabled both with:
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
Because of the fact that some functionality on desktop is provided by update-manager and
I do not want to get error messages about lock-files in archives or lists directories whenever I run apt manually.
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
add a comment |
You can decide it by yourself. But on my systems (mainly 16.04 LTS) I have disabled both with:
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
Because of the fact that some functionality on desktop is provided by update-manager and
I do not want to get error messages about lock-files in archives or lists directories whenever I run apt manually.
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
add a comment |
You can decide it by yourself. But on my systems (mainly 16.04 LTS) I have disabled both with:
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
Because of the fact that some functionality on desktop is provided by update-manager and
I do not want to get error messages about lock-files in archives or lists directories whenever I run apt manually.
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
You can decide it by yourself. But on my systems (mainly 16.04 LTS) I have disabled both with:
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
Because of the fact that some functionality on desktop is provided by update-manager and
I do not want to get error messages about lock-files in archives or lists directories whenever I run apt manually.
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
answered May 22 '18 at 19:43
N0rbertN0rbert
23.5k649111
23.5k649111
add a comment |
add a comment |
Yes, it is important, you need it.
If spending internet data is a concern to you like it is to me, you may not want it to be started so often.
But that is useful to keep your OS secure by keeping packages updated.
Now about the slow startup, others already answered how to workaround that :)
add a comment |
Yes, it is important, you need it.
If spending internet data is a concern to you like it is to me, you may not want it to be started so often.
But that is useful to keep your OS secure by keeping packages updated.
Now about the slow startup, others already answered how to workaround that :)
add a comment |
Yes, it is important, you need it.
If spending internet data is a concern to you like it is to me, you may not want it to be started so often.
But that is useful to keep your OS secure by keeping packages updated.
Now about the slow startup, others already answered how to workaround that :)
Yes, it is important, you need it.
If spending internet data is a concern to you like it is to me, you may not want it to be started so often.
But that is useful to keep your OS secure by keeping packages updated.
Now about the slow startup, others already answered how to workaround that :)
answered Jan 26 at 19:04
community wiki
Aquarius Power
add a comment |
add a comment |
You can change the timer of the service, it should run after the boot, actually.
Here's the solution.
Ubuntu 16.04 slow boot (apt-daily.service)
As a workaround, do sudo systemctl edit apt-daily.timer and paste the following text into the editor window:
# apt-daily timer configuration override
[Timer]
OnBootSec=15min
OnUnitActiveSec=1d
AccuracySec=1h
RandomizedDelaySec=30min
This changes the "timer" that triggers apt-daily.service to run at a random time between 15 min and 45 min after boot, and once a day thereafter. See the systemd.timer manpage for additional (not very well written, alas) explanation of what this means.
If this is not working, create/edit the file in /etc/systemd/system/apt-daily.timer
edited 6 hours ago
gman
1,07331531
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
add a comment |
You can change the timer of the service, it should run after the boot, actually.
Here's the solution.
Ubuntu 16.04 slow boot (apt-daily.service)
As a workaround, do sudo systemctl edit apt-daily.timer and paste the following text into the editor window:
# apt-daily timer configuration override
[Timer]
OnBootSec=15min
OnUnitActiveSec=1d
AccuracySec=1h
RandomizedDelaySec=30min
This changes the "timer" that triggers apt-daily.service to run at a random time between 15 min and 45 min after boot, and once a day thereafter. See the systemd.timer manpage for additional (not very well written, alas) explanation of what this means.
If this is not working, create/edit the file in /etc/systemd/system/apt-daily.timer
edited 6 hours ago
gman
1,07331531
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
add a comment |
You can change the timer of the service, it should run after the boot, actually.
Here's the solution.
Ubuntu 16.04 slow boot (apt-daily.service)
As a workaround, do sudo systemctl edit apt-daily.timer and paste the following text into the editor window:
# apt-daily timer configuration override
[Timer]
OnBootSec=15min
OnUnitActiveSec=1d
AccuracySec=1h
RandomizedDelaySec=30min
This changes the "timer" that triggers apt-daily.service to run at a random time between 15 min and 45 min after boot, and once a day thereafter. See the systemd.timer manpage for additional (not very well written, alas) explanation of what this means.
If this is not working, create/edit the file in /etc/systemd/system/apt-daily.timer
edited 6 hours ago
gman
1,07331531
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
You can change the timer of the service, it should run after the boot, actually.
Here's the solution.
Ubuntu 16.04 slow boot (apt-daily.service)
As a workaround, do sudo systemctl edit apt-daily.timer and paste the following text into the editor window:
# apt-daily timer configuration override
[Timer]
OnBootSec=15min
OnUnitActiveSec=1d
AccuracySec=1h
RandomizedDelaySec=30min
This changes the "timer" that triggers apt-daily.service to run at a random time between 15 min and 45 min after boot, and once a day thereafter. See the systemd.timer manpage for additional (not very well written, alas) explanation of what this means.
If this is not working, create/edit the file in /etc/systemd/system/apt-daily.timer
edited 6 hours ago
gman
1,07331531
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
edited 6 hours ago
gman
1,07331531
edited 6 hours ago
gman
1,07331531
edited 6 hours ago
gman
1,07331531
1,07331531
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
answered Oct 21 '18 at 1:08
overkill22overkill22
1166
1166
add a comment |
add a comment |
protected by N0rbert Dec 23 '18 at 16:29
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
See Debian Bug #844453 for a complete explanation of the issue, and current work in progress to fix.
– user535733
May 22 '18 at 11:48