Hello; Not sure if this helps, but from the bug tracker, it looks like the error message could be avoided if warnings are turned off or if you pre-declare the variable that is empty. Regards; John
-----Original Message----- From: Jonas Meurer [mailto:jo...@freesources.org] Sent: Monday, March 11, 2013 6:39 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] empty arguments bug in ePN Hello, while switching from external perl interpreter to ePN, we stumbled over the empty arguments bug in ePN (http://tracker.nagios.org/view.php?id=88). This bug keeps us from using ePN for a lot of the check commands we use. Does anybody know a Nagios fix for that (not one that involves patching all the plugin scripts)? Kind regards, jonas ---------------------------------------------------------------------------- -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null