<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jan,<br>
<br>
If we only use $ARG1$, we need to update all of the documentation that
ships with the Nagios packages. For example, the sample windows.cfg
file that ships with nagios3-common includes the following code:<br>
<pre class="message">define service{
use generic-service
host_name winserver
service_description Memory Usage
check_command check_nt!MEMUSE!-w 80 -c 90
}
</pre>
This matches the documentation that ships with nagios3-doc as well as
the upstream documentation. We could, of course, change all our
internal documentation, but adding $ARG2$ makes the Debian packages
function more closely like the upstream and has no negative impact on
existing installations because $ARG2$ is ignored if empty.<br>
<br>
<div class="moz-signature">
<title></title>
<font color="#000000">Soren Stoutner</font><br>
</div>
<br>
Jan Wagner wrote:
<blockquote cite="mid:200905122132.54446.waja@cyconet.org" type="cite">
<pre wrap="">Hi Sven,
On Tuesday 12 May 2009, Sven Velt wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I *would* prefer "check_nscp" as the author named the software. But yes,
it would be a nice solution (independent of chosen command_name) for the
Debian packages.
</pre>
</blockquote>
<pre wrap=""><!---->
okay ... point taken. :)
</pre>
<blockquote type="cite">
<pre wrap="">Maybe we could add another one with "-l '$ARGV2'" add... ;-)
</pre>
</blockquote>
<pre wrap=""><!---->
Hmm ... I personly prefer general solutions and the one just with $ARGV1 is
one in my eyes ... beside the documentaion shipped with nagios (upstream and
with our package), where they use also $ARGV2, we didn't reference anything
about such a way in our package. Why should we use different checks, if we
can do the same with one?
For example "check_command check_nt!'MEMUSE -w 80 -c 90'" works like a charm.
With kind regards, Jan.
</pre>
</blockquote>
</body>
</html>