<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Syslog on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/syslog/</link>
    <description>Recent content in Syslog on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 20 Sep 2026 11:59:22 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/syslog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Eliminating 10,000‑Line DHCP Server Spam in Syslog Without Disabling the Service</title>
      <link>https://linuxeries.org/post/2026-09-20-eliminating-10000line-dhcp-server-spam-in-sys/</link>
      <pubDate>Sun, 20 Sep 2026 11:59:22 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-09-20-eliminating-10000line-dhcp-server-spam-in-sys/</guid>
      <description>&lt;h2 id=&#34;problem-dhcp-spamming-syslog&#34;&gt;Problem: DHCP Spamming Syslog&lt;/h2&gt;&#xA;&lt;p&gt;A running DHCP server can generate thousands of “client request” and “lease granted” messages every hour. On busy networks this inflates &lt;code&gt;/var/log/syslog&lt;/code&gt; to 10 k lines a day, making it hard to spot genuine errors and bloating disk usage. The service must stay online, so the goal is to silence the noise without turning the daemon off.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-you-cant-just-disable-the-service&#34;&gt;Why You Can’t Just Disable the Service&lt;/h2&gt;&#xA;&lt;p&gt;Disabling &lt;code&gt;dhcpd&lt;/code&gt; or &lt;code&gt;dhcp-server&lt;/code&gt; removes the spam but also removes the ability to hand out IPs. In a homelab or small office you may have a separate DHCP server (e.g., a router) that you can stop, but in many setups the Linux box is the sole DHCP provider. The logs are useful for troubleshooting mis‑configurations, but the volume is excessive.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
