<?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 Technical Notes</title><link>http://luispa.com/en/tags/systemd/</link><description>Recent content in Systemd on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sun, 23 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>Daily Reboot with Systemd</title><link>http://luispa.com/en/posts/2023-07-23-systemd-reboot/</link><pubDate>Sun, 23 Jul 2023 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2023-07-23-systemd-reboot/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-systemd-reboot.svg" alt="systemd reboot logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>To perform a full reboot you can use the &lt;code>systemctl reboot&lt;/code> command, but how can you schedule it at a specific time? In this post I explain how to do it using &lt;a href="https://systemd.io/">systemd&lt;/a>, the boot manager and administration system for Linux distributions.&lt;/p>
&lt;p>Among the &lt;em>&lt;strong>systemd timer services&lt;/strong>&lt;/em> there&amp;rsquo;s a little-known feature that allows you to schedule an automatic reboot whenever you want.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Socketed SSH</title><link>http://luispa.com/en/posts/2023-04-14-ssh-socket/</link><pubDate>Fri, 14 Apr 2023 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2023-04-14-ssh-socket/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-socketed-ssh.svg" alt="socketed ssh logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>&lt;a href="https://systemd.io">Systemd&lt;/a> is a system used in Linux to manage boot and system processes. Its &lt;strong>&amp;ldquo;units&amp;rdquo;&lt;/strong> are configuration files that describe the processes and services that &lt;code>systemd&lt;/code> manages.&lt;/p>
&lt;p>One of these units is &lt;code>systemd.socket&lt;/code>, which starts the corresponding daemon when a connection is established through a socket with the machine. A socket is a form of communication between processes over a network or within the system. By creating a unit of this type, we ask it to listen on a specific socket and start a specific service when a connection is received.&lt;/p>
&lt;br clear="left"/></description></item><item><title>User Systemd Services</title><link>http://luispa.com/en/posts/2021-05-30-systemd-usuario/</link><pubDate>Sun, 30 May 2021 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2021-05-30-systemd-usuario/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-systemd.svg" alt="systemd logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>The &lt;a href="https://systemd.io/">systemd&lt;/a> manager allows configuring services from a normal system user. These &lt;em>&lt;strong>systemd user services&lt;/strong>&lt;/em> are a little-known but very useful feature. It consists of being able to create and use &lt;code>.service&lt;/code> files from a user&amp;rsquo;s local directory that run with their privileges.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Static IP with Systemd on Gentoo</title><link>http://luispa.com/en/posts/2013-12-23-ip-fija-systemd/</link><pubDate>Mon, 23 Dec 2013 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2013-12-23-ip-fija-systemd/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-ip.svg" alt="Static IP" width="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe how to configure a static IP address on a Linux machine based on Gentoo. Normally this operating system comes pre-configured to load a dynamic IP address via the DHCP protocol.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>