On Wed, 30 Nov 2005, Aleksey Tsalolikhin wrote:
> command_line $USER1$/check_mysql -H $ARG1$ -d $ARG2$ -u
> $ARG3$ -p $ARG4$
Why not use $USER4$ here?
> check_command
> check_mysql!192.168.160.2!mydbname!mydbusername!mydbpassword
> check_command
> check_mysql!192.168.160.2!mydbname!mydbusername!$USER4$
>
> and setting $USER4$ in resource.cfg, I get error
I think not all files will support variables the way you think. But this
time you have passed a password named $USER4$ instead of the variable.
Hugo.
--
I hate duplicates. Just reply to the relevant mailinglist.
[EMAIL PROTECTED] http://hvdkooij.xs4all.nl/
Don't meddle in the affairs of magicians,
for they are subtle and quick to anger.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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
