On Sat, 16 Feb 2019 16:39 Marc Donges <marc.don...@gmail.com wrote: > 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 everything else the sysadmin does > manually on the CLI. >
Here the issue feels much more in munin-run not being the same as munin-node. That systemd configuration is new from stretch IMHO, but I think it is for the better nowadays. I think to make this less awkward two things would be nice: > That said, I agree that we should make it more obvious. - 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 of my problem, but I suppose it will be overwritten on every > update. Is there a nice way to do this?) > You can always copy the file into /etc, it will then take precedence - a way to alert the admin of the possibly unintended configuration: > df-plugin activated + ProtectHome + Separate /home > This can be done inside the munin-run environment, and not only for the df plugin. Can the df* plugin itself detect the situation and then make a log entry? > That would have severely cut down the time it took me to find this. > I have to see if the df plugin does know about it, as I'm not sure it can detect it reliably. -- Steve Schnepp >
