Hi Guy, Many thanks for your post. I decided to go with Option (1) as per your description and did the following in the nrpe.cfg file on the monitored host: command[check_disk]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p / command[check_var]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var command[check_server1]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var/opt/BGw/Server1 command[check_ora]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var/opt/mediation/ora And then on the nagios monitoring server I have this: define service{ use generic-service ; Name of service template to use host_name emm4 service_description Root Partition check_command check_nrpe!check_disk!15%!10%! } define service{ use generic-service ; Name of service template to use host_name emm4 service_description var Partition check_command check_nrpe!check_var!30%!20%! } define service{ use generic-service ; Name of service template to use host_name emm4 service_description server1 Partition check_command check_nrpe!check_server1!30%!20%! } define service{ use generic-service ; Name of service template to use host_name emm4 service_description ora Partition check_command check_nrpe!check_ora!30%!20%! } When I log into the nagios Web GUI, the services for the ora, server1 and var partition have been successfully created. However, looking at the "status information" column, I have the following errors: "NRPE: Command 'check_ora' not defined" "NRPE: Command 'check_server1' not defined" "NRPE: Command 'check_var' not defined" This indicates that I need to explicitly define 'check_ora', 'check_server1' and 'check_var' elsewhere. So, where else must I define these services so as to clear out the errors above? Thanks in advance! <div class="gmail_quote">2009/7/15 Guy Waugh <<a href="mailto:guidosh@gmail.com">guidosh@gmail.com</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi Juki, As I understand it, you can either (1) 'hard-code' your NRPE checks in the nrpe.cfg file on the monitored host (so that the checks are explicitly defined), or (2) set up NRPE on the monitored host in such a way that you can pass arguments in your NRPE checks. It looks like you're landing somewhere between the two with your configuration. I would either go the Option (1) way, having something like this in your nrpe.cfg file on the monitored host: command[check_root]=/usr/local/nagios/libexec/check_disk -w 30% -c 15% -p / command[check_var]=/usr/local/nagios/libexec/check_disk -w 30% -c 15% -p /var command[check_server1]=/usr/local/nagios/libexec/check_disk -w 30% -c 15% -p /var/opt/BGw/Server1 command[check_ora]=/usr/local/nagios/libexec/check_disk -w 30% -c 15% -p /var/opt/mediation/ora , and then having services on the nagios host like this: <div class="im">define service{ use generic-service ; Name of service template to use host_name emm4 service_description Root Partition </div> check_command check_nrpe!check_root } Alternatively, for the Option (2) method, on the monitored host, in nrpe.cfg: command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$ , and a service example on the nagios host: <div class="im">define service{ use generic-service ; Name of service template to use host_name emm4 service_description Root Partition </div> check_command check_nrpe!check_disk!30!15!/ } I may not have the syntax in the 'check_command' of that last service exactly right, but that's the general idea. To go down the Option 2 road, you have to have configured the NRPE daemon on the monitored host with '--enable-command-args', and have to have a line in your nrpe.cfg file that says 'dont_blame_nrpe=1'. This is because allowing command arguments in this fashion can be a security risk. The default nrpe.cfg file has some comments that refer to this. HTH, Guy. </blockquote></div>