resource.cfg variables in services as arguments

[John Borwick]

Hello.  I would like to be able to have several community strings for 
the same check_command, without exposing them in my service 
configuration files.  I would really like to be able to say

   check_command                   my_snmp_check!$USER1$

in a "service" statement.  I believe "$USER1$" is treated as a literal 
in this context.

When I replace $ARG1$ with $USER1$ in the check itself, or $USER1$ in 
the service with the actual community string, then the SNMP query finds 
the community string and works fine.

Am I doing anything wrong?  Is the above (treating "$USER1$" as a 
literal) the intended action?  Do people just not pass resource strings 
inside service statements?

Thank you very much.

Yours,
John
-- 
            John Borwick
        System Administrator
       Wake Forest University | web  http://www.wfu.edu/~borwicjh
       Winston-Salem, NC, USA | GPG key ID             0x797326D5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
URL: <https://www.monitoring-lists.org/archive/users/attachments/20041110/9b3db253/attachment.sig>