Hi,
I've applied the proposed solution (using $ENV{MUNIN_APT_RELEASES}) but
ran into an unsuspected issue:
munin-node package creates a cron jobs file ("/etc/cron.d/munin-node")
where it directly runs the apt_all plugin, as an executable script, not
through Munin's system (like `munin-run` would), thus not taking
munin-node configuration into account.
# If the APT plugin is enabled, update packages databases approx. once
# an hour (12 invokations an hour, 1 in 12 chance that the update will
# happen), but ensure that there will never be more than two hour (7200
# seconds) interval between updates..
*/5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi
My naive attempt to fix this was to replace direct
`/etc/munin/plugins/apt_all update 7200 12`
calls with a
`munin-run apt_all update 7200 12`
But sadly munin-run don't push the extra "7200" and "12" parameters to
the apt_all, which in turns only has "update" in it's $ARGV and sees it
as an error and display the helping usage text:
# munin-run apt_all update 7200 12
apt update <maxinterval> <probability> -- update apt databases randomly
maxinterval:
Enforce the updating of the apt database if it has
been more than (maxinterval many seconds since the last update.
probability:
There's a 1 in (probability) chance that the database
will be updated.
I'm not sure how this could be easily solved.
--
Duvergier Claude
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
