<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Servidor on Servicios Rogeliowar</title><link>https://blog.serviciosrogeliowar.com/en/tags/servidor/</link><description>Recent content in Servidor on Servicios Rogeliowar</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Rogelio Guerra Riverón</copyright><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.serviciosrogeliowar.com/en/tags/servidor/index.xml" rel="self" type="application/rss+xml"/><item><title>Systemd timers: the modern cron alternative you needed</title><link>https://blog.serviciosrogeliowar.com/en/posts/systemd-timers-la-alternativa-moderna-a-cron-que-necesitabas/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://blog.serviciosrogeliowar.com/en/posts/systemd-timers-la-alternativa-moderna-a-cron-que-necesitabas/</guid><description>&lt;h2 class="relative group"&gt;Why I Left Cron
 &lt;div id="why-i-left-cron" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-i-left-cron" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;ve been using cron on my servers for years. It&amp;rsquo;s simple, reliable, and it works. But recently I discovered systemd timers and I&amp;rsquo;m not going back. The main reason: &lt;strong&gt;integrated logs in journald&lt;/strong&gt;, no &lt;code&gt;.log&lt;/code&gt; files scattered around the system, and better control over what happens when the server starts or reboots.&lt;/p&gt;
&lt;p&gt;In my specific case, I had a backup that wouldn&amp;rsquo;t run if the server was off at the scheduled time. With cron, it simply got lost. With systemd timers and &lt;code&gt;Persistent=true&lt;/code&gt;, the task runs as soon as the server boots up.&lt;/p&gt;</description></item><item><title>Security email notifications from the terminal with msmtp and Gmail</title><link>https://blog.serviciosrogeliowar.com/en/posts/notificaciones-de-seguridad-por-email-desde-el-terminal-con-msmtp-y-gmail/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.serviciosrogeliowar.com/en/posts/notificaciones-de-seguridad-por-email-desde-el-terminal-con-msmtp-y-gmail/</guid><description>&lt;h2 class="relative group"&gt;Why you need this
 &lt;div id="why-you-need-this" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-you-need-this" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;When you run a server at home, you need to know if something strange happens. A script that sends you an email when it detects a failed login attempt, an expiring certificate, or a nearly full disk is invaluable. The problem is that your ISP blocks port 25, so you can&amp;rsquo;t use sendmail directly. That&amp;rsquo;s where msmtp comes in.&lt;/p&gt;</description></item></channel></rss>