<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Systemd on ae3.ch</title>
    <link>https://ae3.ch/tags/systemd/</link>
    <description>Recent content in Systemd on ae3.ch</description>
    <image>
      <title>ae3.ch</title>
      <url>https://ae3.ch/ae3-og.png</url>
      <link>https://ae3.ch/ae3-og.png</link>
    </image>
    <generator>Hugo -- 0.154.5</generator>
    <language>en</language>
    <lastBuildDate>Thu, 29 Dec 2022 23:35:48 +0100</lastBuildDate>
    <atom:link href="https://ae3.ch/tags/systemd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Systemd timer as a cron replacement</title>
      <link>https://ae3.ch/systemd-timer-as-a-cron-replacement/</link>
      <pubDate>Thu, 29 Dec 2022 23:35:48 +0100</pubDate>
      <guid>https://ae3.ch/systemd-timer-as-a-cron-replacement/</guid>
      <description>&lt;p&gt;Instead of using a cronjob placed in our crontab, we can make use of a systemd timer on a modern linux system which is running systemd.&lt;/p&gt;
&lt;p&gt;For a systemd timer to work, it needs two parts.
One part consists of a &lt;code&gt;.timer&lt;/code&gt; file, and a &lt;code&gt;.service&lt;/code&gt; file.&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;.timer&lt;/code&gt; file specifies when our service should be started. Just like a cronjob we can specify here on which days, in which week or at which time our service should be started.
Our &lt;code&gt;.service&lt;/code&gt; file contains all the details about the script or command we want to run.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
