<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Marc JESTIN's Blog</title><link>https://blog.marcjestin.fr/en/categories/devops/</link><description>Recent content in DevOps on Marc JESTIN's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.marcjestin.fr/en/categories/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Preventing sleep and suspension on a Debian server</title><link>https://blog.marcjestin.fr/en/posts/preventing-sleep-and-suspension-on-a-debian-server/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://blog.marcjestin.fr/en/posts/preventing-sleep-and-suspension-on-a-debian-server/</guid><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;A server must be available 24 hours a day and obviously should not go to sleep, especially if we don&amp;rsquo;t have the tools to &amp;ldquo;wake it up.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;By default, or following the installation of certain packages, a &lt;code&gt;Debian&lt;/code&gt; distribution may retain power-saving settings. The result: our machine &amp;ldquo;falls asleep&amp;rdquo; after a period of inactivity, and we can no longer access it remotely. &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;This is particularly true for systems installed in a &lt;code&gt;Desktop&lt;/code&gt; version (i.e., with a desktop manager like &lt;code&gt;GNOME&lt;/code&gt; or others).&lt;/p&gt;</description></item><item><title>Using ACLs for Advanced File and Directory Permissions in Debian</title><link>https://blog.marcjestin.fr/en/posts/using-acls-for-advanced-file-and-directory-permissions-in-debian/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://blog.marcjestin.fr/en/posts/using-acls-for-advanced-file-and-directory-permissions-in-debian/</guid><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;We often find ourselves working in directories where multiple users &amp;ldquo;clash&amp;rdquo; with one another.&lt;/p&gt;
&lt;p&gt;A common example is when we need to clear caches generated by web server components. We then run into ownership and permission issues.&lt;/p&gt;
&lt;p&gt;Usually, we rely on &amp;ldquo;bad good solutions&amp;rdquo;, such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Adding our user to a group it doesn&amp;rsquo;t truly belong to.&lt;/li&gt;
&lt;li&gt;Creating custom &lt;code&gt;sudo&lt;/code&gt; rules (which often end up being too broad, creating a significant security loophole).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Managing &lt;code&gt;ACLs&lt;/code&gt; in Debian allows us to handle this very simply.&lt;/p&gt;</description></item></channel></rss>