Package: munin-plugins-core
Followup-For: Bug #863231
Control: retitle -1 Plugins "apt" and "apt_all" use state file with same name
in different locations
Control: forwarded -1 https://github.com/munin-monitoring/munin/issues/1072
Hello,
ok - I took another look at the issue. Sadly it is a bit m
On Sat, 23 Jun 2018 02:51 Lars Kruse, wrote:
> Otherwise we will run apt_all as
> root (as suggested above).
>
That would be the obvious fix, as we do not mix statefiles from different
users in the same directory for security purposes.
It is much easier to secure a whole directory than individu
Hi,
Am Sat, 23 Jun 2018 01:03:44 +0200
schrieb Lars Kruse :
> I just checked here, whether it would be sufficient to simply run the cron-job
> as "nobody" (instead of root). This works for me.
> This would be preferable (compared to the change above), or?
> Or maybe I overlooked something?
inde
Hi,
Am Wed, 24 May 2017 09:40:49 +
schrieb Holger Levsen :
> > Adding the following to /etc/munin/plugin-config.d/munin-node fixed it
> > for me:
> >
> > [apt_all]
> > user root
> > env.MUNIN_PLUGSTATE /var/lib/munin-node/plugin-state/nobody/
> >
> > I'm not sure if that's the correct fix, t
control: severity -1 normal
thanks
Hi Benjamin,
thanks for your bug report! I've lowered the severity because a misconfigured
plugin doesn't have a major impact on the packageā¦
On Wed, May 24, 2017 at 09:57:36AM +0200, Benjamin Schieder wrote:
> the apt_all plugin reads from a different statefi
Package: munin-plugins-core
Version: 2.0.33-1
Severity: important
Dear Maintainer,
the apt_all plugin reads from a different statefile than the included
cronjob writes to.
File read from: /var/lib/munin-node/plugin-state/root/plugin-apt.state
File written to: /var/lib/munin-node/plugin-state/nob
6 matches
Mail list logo