Monitoring 64-bit and 32-bit servers - plugin path problem

[Gavin Carr]

On Tue, Sep 23, 2008 at 04:42:45PM -0300, Marcel wrote:
> I think you missed the point Andreas tried to make.
> 
> On Tue, Sep 23, 2008 at 5:48 AM, Kenneth Holter <kenneho.ndu at gmail.com>wrote:
> 
> > Actually, I've done this already. The macro, say, X defines the path to be
> > "/usr/lib64/nagios/plugins". But as far as I can see this does not solve my
> > problem, as the path on a 32-bit systems is different than the path on a
> > 64-bit system.
> >
> 
> Let's say you have $USER1$ = /path/to/lib32/nagios/plugins, and
> $USER2$=/path/to/lib64/nagios/plugins, thus, you should define x86_32
> commands and x86_64 commands as usual, but using $USER1$ and $USER2$ where
> pertinent, and then, on every x64 system, you should use the _64 commands.

Although that's a bit of an ugly solution, as you're having to define every 
command twice. DRY etc.

We've found it easier to just leave the plugin invocations unqualified and add
the relevant nagios plugins directory to the $PATH for the remote nagios user.
Works nicely here.

Cheers,
Gavin


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at 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