<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cron on Ramblings from bkero</title>
    <link>https://bke.ro/tags/cron/</link>
    <description>Recent content in Cron on Ramblings from bkero</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 30 Apr 2010 18:58:35 +0000</lastBuildDate>
    <atom:link href="https://bke.ro/tags/cron/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Munin-cron overlap fix</title>
      <link>https://bke.ro/munin-cron-overlap-fix/</link>
      <pubDate>Fri, 30 Apr 2010 18:58:35 +0000</pubDate>
      <guid>https://bke.ro/munin-cron-overlap-fix/</guid>
      <description>&lt;p&gt;One solution I tried was to turn up the time between tests from 5 minutes to 10 minutes. This still had generated problems, as munin-cron runs still weren&amp;rsquo;t done after 10 minutes, and any greater time between polls meant subpar graph granularity.&lt;/p&gt;&#xA;&lt;p&gt;My final solution was to modify munin&amp;rsquo;s cron entry to the following:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;*/7 * * * *     munin test ( ! &amp;#34;$(pidof /usr/bin/munin-cron)&amp;#34; ) &amp;amp;&amp;amp; test -x /usr/bin/munin-cron &amp;amp;&amp;amp; nice -19 /usr/bin/munin-cron&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;I ran a test to see if there&amp;rsquo;s still a PID active from munin-cron, and if not check to see if the munin-cron executable exists. If it does exist, run a munin-cron job with the nicest setting possible.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
