Hello Laurence,
thank you for sharing your thoughts!
On Tue, 7 Jan 2020 08:54:23 + Laurence Parry wrote:
> [..]
> The [df*] section in the plugins.conf file (aka plugins-conf/munin-node)
> could contain a comment regarding this situation. That's the first place I
> went to look, to see if
I appreciate the concern of Debian developers for the security of their
users' data.
However, I also spent too long debugging this problem, going through the
same process of "it works in munin-run, it works if I run munin-node from
the command line; why isn't it working?"
The behaviour *is*
On Tue, Sep 03, 2019 at 05:11:55PM +0200, Ferenc Wágner wrote:
> Today I noticed that my /home mount is not graphed by the df plugin
> against my expectations.
I'm sorry this doesnt match *your* expectations but I have to say this
behaviour *does* match many other peoples expectations including
writes:
> yes, there were also a few issues raised and a few questions asked via IRC.
> The difference between executing "munin-run" and deploying the plugin in a
> real
> environment can be an annoying source of confusion.
> But the hardening directives can be of really good use, since they
Hello,
thank you for your suggestion!
Am Tue, 03 Sep 2019 17:11:55 +0200
schrieb Ferenc Wágner :
> Today I noticed that my /home mount is not graphed by the df plugin
> against my expectations. After too much debugging I realized that the
> ProtectHome=true setting in
Package: munin-node
Version: 2.0.49-1~bpo9+1
Severity: normal
Dear Maintainer,
Today I noticed that my /home mount is not graphed by the df plugin
against my expectations. After too much debugging I realized that the
ProtectHome=true setting in /lib/systemd/system/munin-node.service
causes the
6 matches
Mail list logo
