[Stig Sandbeck Mathisen] > Munin-cron does not have locking, since we need to run munin-update even > if munin-graph is running from a previous munin-cron. > > The underlying scripts have sufficient locking. On a maching with > insufficient resources, munin may break either way, since it needs to be > able to complete munin-update every 5 minutes to gather sufficient data.
The consequence on a machine with insufficient resources, is that munin will spend all resources and bring the machine to complete standstill. The first job starts, then the next job starts before the first job is finished and slow down the machine even more, and then the third job starts before the second and perhaps also the first job is finished, and so on. This is the failure mode I suggest to implement a guard against. Yes, in any case munin will not work properly, but at least it will be possible to try to fix it. :) munin-node made it impossible to log into the machine in question. :/ Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
