<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Systemd on Puppeteers Oy</title>
		<link>https://www.puppeteers.net/tags/systemd/</link>
		<description>Recent content in Systemd on Puppeteers Oy</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Wed, 05 Aug 2020 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.puppeteers.net/tags/systemd/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Taming apt timers in Ubuntu 18.04</title>
				<link>https://www.puppeteers.net/blog/taming-apt-timers-in-ubuntu-18-04/</link>
				<pubDate>Wed, 05 Aug 2020 00:00:00 +0000</pubDate>
				<guid>https://www.puppeteers.net/blog/taming-apt-timers-in-ubuntu-18-04/</guid>
				<description>&lt;p&gt;Ubuntu 18.04 AWS images - and probably other Cloud images as well - have automated upgrades turned on. This is done via two &lt;a href=&#34;https://www.freedesktop.org/software/systemd/man/systemd.timer.html&#34;&gt;systemd timers&lt;/a&gt;, &lt;em&gt;apt-daily.timer&lt;/em&gt; and &lt;em&gt;apt-daily-upgrade.timer&lt;/em&gt;. The timers kick of periodically as well as when an instance is rebooted. This sounds reasonable until you are provisioning something: you&amp;rsquo;re unable to install or configure any packages while apt and/or dpkg are running. With a really fresh cloud base image this &lt;em&gt;may&lt;/em&gt; not be an issue, but when the base image gets sufficiently old then &lt;em&gt;apt-get upgrade&lt;/em&gt; starts taking enough time to cause issues.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
