<?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>C on Alexander's Blog</title><link>https://alexanderbakin.com/tags/c/</link><description>Recent content in C on Alexander's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 17:54:01 +0400</lastBuildDate><atom:link href="https://alexanderbakin.com/tags/c/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing logrotate's Glob Confusion</title><link>https://alexanderbakin.com/logrotate-fix/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>https://alexanderbakin.com/logrotate-fix/</guid><description>&lt;p&gt;A follow-up to &lt;a href="https://alexanderbakin.com/logrotate-wildcard-bug/"&gt;the wildcard bug post&lt;/a&gt; from last year.&lt;/p&gt;
&lt;h2 id="picking-the-thread-back-up"&gt;Picking the Thread Back Up&lt;/h2&gt;
&lt;p&gt;The rename workaround, &lt;code&gt;*.example.com&lt;/code&gt; to &lt;code&gt;_.example.com&lt;/code&gt;, fully resolved the operational problem. Retention became predictable again, and there was no pressing reason to go further. But a workaround isn&amp;rsquo;t a fix, and the actual bug was still sitting in logrotate&amp;rsquo;s own source, waiting to bite the next person who names a file after a wildcard domain. This week I finally sat down and found it properly, instead of just renaming files around it.&lt;/p&gt;</description></item></channel></rss>