[Pkg-nagios-devel] Bug#528262: Bug#528262: Bug#528262: Bug#528262: Bug#528262: nagios-plugins-standard: Error in command_line in nt.cfg causes errors

[Jan Wagner]

Hi Soren,

On Tuesday 12 May 2009, Soren Stoutner wrote:
> I understand that I could change my setup to work with one argument as
> you have listed below.  I'm simply stating that all the documentation,
> both on the nagios.org website, nsclient.org, and the documentation that
> ships with the various Debian Nagios packages are following a
> standardized way of doing things.  Why don't we change the way the
> Debian packages are configured to match that standard, documented
> method.  I see two advantages:

could you please clearly point to the exact parts of each of the 
documentations you are refering to? For now I did found onyl the 
documentation provided on nagios.org[1] and the one shiped[2] with 
nagios3-common, which is the same.
From my point of view, the developer(s) of nagios just advised using check_nt 
in wrong way. check_nt is part of nagios-plugins and not nagios[123], so it 
is 3rd party from their viewpoint. Maybe they find it elegant todo it in this 
way, but there may also other opinions. Suggesting the use of the plugin in 
any way on nagios.org and in the nagios distribution doesn't postulate the 
ultimate way, how a plugin has to be used.
Imagine your ISP dictates you, how to use you computers, just cause you can 
use it with his internet connection.

> Alternately, if bringing check_nt into compliance with the documentation
> isn't a viable option, then we need to file bugs against each of the
> Debian documentation packages so that they accurately reflect how
> Debian's Nagios installation runs.

I saw you filled a bug against nagios3-common, that maybe reasonable. But the 
problem is upstream, I would say. What else packages are you referencing?

Beside that discussion, if you setup your nagios environment, don't you need 
to read documentation (, okay .. you did, but unfortunatly not the best 
part :)) and if anything fails with your check(s), don't you need to search 
the command definitions and think about, if they make sence for your setup?
I personly prefer to recommand to use additional files 
in /etc/nagios-plugins/config/ or /etc/nagios3/conf.d/ for highly customised 
command definitions.

Anyways .. did you check the command definitions I suggested you?

Thanks and with kind regards, Jan.
[1] http://nagios.sourceforge.net/docs/3_0/monitoring-windows.html
[2] /usr/share/nagios3/htdocs/docs/monitoring-windows.html 
-- 
Never write mail to <waja at spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-nagios-devel/attachments/20090513/2857ad40/attachment.pgp>