I think you missed the point Andreas tried to make.

On Tue, Sep 23, 2008 at 5:48 AM, Kenneth Holter <[EMAIL PROTECTED]>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.

HTH,
Marcel


>
>
> On 9/23/08, Andreas Ericsson <[EMAIL PROTECTED]> wrote:
>>
>> Kenneth Holter wrote:
>>
>>> Hello all.
>>>
>>>
>>> I've set up Nagios to monitor a few 64-bit machines, and this seems to be
>>> working correctly. For example, my command for checking a remote disk is
>>> defined like this:
>>>
>>>
>>> define command{
>>>        command_name    check_remote_disk
>>>        command_line    /somepath/check_by_ssh <args> -C
>>> "/usr/lib64/nagios/plugins/check_disk <remote args>"
>>> }
>>>
>>> This command executes /usr/*lib64*/nagios/plugins/check_disk on the
>>> remote
>>> system. On 32-bit systems, on the other hand, the path to the plugin is
>>> /usr/*lib*/nagios/plugins/check_disk. It thus looks like I have to
>>> differentiate between 32-bit and 64-bit commands, and in effect devide
>>> the
>>> configuration itself in a 32-bit section and 64-bit section.
>>>
>>> I'm sure there is a neat way of solving this, and could use some advice.
>>> I
>>> guess I could symlink all over the place to get things going, but there
>>> are
>>> probably a better way of doing this.
>>>
>>>
>> Modify resource.cfg and use a macro to define the path to the plugins.
>>
>> --
>> Andreas Ericsson                   [EMAIL PROTECTED]
>> OP5 AB                             www.op5.se
>> Tel: +46 8-230225                  Fax: +46 8-230231
>>
>
>
> -------------------------------------------------------------------------
> 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@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
>
-------------------------------------------------------------------------
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@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

Reply via email to