On Wed, Feb 20, 2019 at 09:00:52PM +0100, Lars Kruse wrote:
> > I might be naive, but I'm wondering if some debconf dialog to choose at
> > install time might be an option.
> Sounds like a good idea to me.
on irc I commented this:
| sumpfralle: debconf questions are annoying (to get on many
Hello,
Am Wed, 20 Feb 2019 16:05:11 +0100
schrieb Steve Schnepp :
> I might be naive, but I'm wondering if some debconf dialog to choose at
> install time might be an option.
Sounds like a good idea to me.
So we have the following options:
A) mention in README.Debian
B) mention in NEWS
C) ask
On Wed, Feb 20, 2019 at 2:51 PM Marc Donges wrote:
> So although I would change this on machines I run, simply because I need
> to know when /home is almost full, I understand that a default install
> would not allow that.
>
I might be naive, but I'm wondering if some debconf dialog to choose
Hi Lars,
On Mon, 18 Feb 2019 at 00:06, Lars Kruse wrote:
> By accident I stumbled upon "systemctl edit munin-node".
> This will open up an empty editor. Here you can add the following:
>
> [Service]
> ProtectHome = read-only
>
> This will create a file
>
Hello,
Am Sat, 16 Feb 2019 16:33:53 +0100
schrieb Marc Donges :
> I think to make this less awkward two things would be nice:
>
> - a option to allow monitoring of /home without editing a non-conffile in
> /lib (How is this even done properly? I just edited the service file to
> find the cause
On Sat, 16 Feb 2019 16:39 Marc Donges However, a separate /home is a common configuration and this problem can
> easily be overlooked and is then not trivial to find, because there are no
> error messages anywhere, there is just this odd difference in reality
> between munin-node as a daemon and
Hi Holger,
thanks for the prompt reply.
I understand the security benefits this presents in combination with
ProtectSystem=full.
However, a separate /home is a common configuration and this problem can
easily be overlooked and is then not trivial to find, because there are no
error messages
Hi Marc,
On Mon, Feb 11, 2019 at 01:09:37AM +0100, Lars Kruse wrote:
> > # Plugins like "df" require access to /home if that is a separate filesystem
> > ProtectHome=false
> See the other bug report for this issue:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918851
> We are discussing
Control: merge -1 918851
Hello Marc,
Am Sun, 10 Feb 2019 22:55:45 +0100
schrieb Marc Donges :
> # Plugins like "df" require access to /home if that is a separate filesystem
> ProtectHome=false
Indeed, this setting prevents your use case.
See the other bug report for this issue:
Package: munin-node
Version: 2.0.45-1
Severity: normal
Dear Maintainer,
on one of my systems I noticed that munin no longer records disk free data for
the separate /home filesystem.
While debugging I could not reproduce the problem when running the df plugin
with munin-run. I could also not
10 matches
Mail list logo
