Some file systems do not have inodes, which make "df" report a "-" instead of a number. If the used and available inode field is not numeric, it does not make sense to try to calculate a percentage. If that happens, we skip calculating inodes for this filesystem.
This basically makes --cron work again.
This already happens for the cgi version.
Without this, the comparison and category pages will create the wrong URL to the images and won't display.
This unbreaks the default generation of the graphs when not installing the CGI (before, it would have worked if the CGI was in place).
kjetilho noticed on IRC that : --- In Ubuntu Precise, the behaviour of setting $0 has changed. If you look in /proc/PID/stat, you will see the given value of $0 exactly. In older distros (kernels?) it would remove the directory part implicitly. I'm not sure if this happens in Perl or in the kernel. But as that field is limited to 15 characters, when $0 = "/usr/sbin/munin-node", what will appear is just "/usr/sbin/munin" which means check_procs -C munin-node in Nagios will fail, pgrep munin-node will fail and so on. --- This commit reverts to the old behavior : "remove the directory part implicitly".
This simplifies the handling of Java being enabled or not, and makes sure that we don't install unusable plugin scripts.
As kjetilho suggested on IRC, In 392659f, the graph_title of if_err was changed to keep nagios-compatibility. But it now occurs that it wasn't optimal to make yet another graph_title. We should keep the graph_title from 1.4 so that users don't have to update their Nagios/Icinga configuration.