Hi all,
I have checked that the fix for LP #1827159 introduces the problem (as kindly said by the reporter) because removing the line corresponding to tmpfs in the fix restores the desired behaviour:
root@nagios-focal:~# df -h | grep reproduce tmpfs 2.0G 0 2.0G 0% /reproduce root@nagios-focal:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -p /reproduce DISK OK - free space: /reproduce 2048 MB (100% inode=99%);| /reproduce=0MB;1843;1945;0;2048
In upstream, it isn't clear to apply the fix for LP #1827159 to tmpfs: https://github.com/monitoring-plugins/monitoring-plugins/pull/1609 and https://github.com/monitoring-plugins/monitoring-plugins/issues/1608
Now, checking the side effects of reverting the fix for tmpfs on the original issue (LP #1827159) ...
Hi all,
I have checked that the fix for LP #1827159 introduces the problem (as kindly said by the reporter) because removing the line corresponding to tmpfs in the fix restores the desired behaviour:
root@nagios- focal:~ # df -h | grep reproduce focal:~ # /usr/lib/ nagios/ plugins/ check_disk -w 10% -c 5% -p /reproduce 0MB;1843; 1945;0; 2048
tmpfs 2.0G 0 2.0G 0% /reproduce
root@nagios-
DISK OK - free space: /reproduce 2048 MB (100% inode=99%);| /reproduce=
In upstream, it isn't clear to apply the fix for LP #1827159 to tmpfs: https:/ /github. com/monitoring- plugins/ monitoring- plugins/ pull/1609 and https:/ /github. com/monitoring- plugins/ monitoring- plugins/ issues/ 1608
Now, checking the side effects of reverting the fix for tmpfs on the original issue (LP #1827159) ...