Bug#332285: closed by Stig Sandbeck Mathisen <[EMAIL PROTECTED]> (Re: Bug#332285: munin-node: cron-job should only run one at the time)

2008-03-10 Thread Petter Reinholdtsen
[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

Bug#332285: munin-node: cron-job should only run one at the time

2005-10-06 Thread Tore Anderson
tags 332285 moreinfo quit * Petter Reinholdtsen > When installing munin-node as part of the debian-edu installation on a > qemu virtual machine, the munin-node cron job take so long to run (or > the clock runts too fast) that several cronjobs are started in > parallel, slowly bringing the machine

Bug#332285: munin-node: cron-job should only run one at the time

2005-10-05 Thread Petter Reinholdtsen
Package: munin-node Version: 1.2.3-1 Severity: normal When installing munin-node as part of the debian-edu installation on a qemu virtual machine, the munin-node cron job take so long to run (or the clock runts too fast) that several cronjobs are started in parallel, slowly bringing the machine t