[Nagiosplug-devel] [RFC] Plugins config file
Ton Voon
ton.voon at altinity.com
Wed Oct 18 17:20:14 CEST 2006
On 18 Oct 2006, at 15:33, sean finney wrote:
>> Which settings do you mean?
>
> i would say as much as possible :) one of the biggest pains
> (historically) with managing installation of the plugins is getting
> them
> to find the utils.pm in the right place (i.e. the susbt script).
Agreed. I want to deprecate utils.pm as soon as possible in favour of
Nagios::Plugin. There's not a huge amount of functionality in there
anyway, as most people have already noted.
> i've also always felt that some of the information in these files
> really
> ought to be treated more as configuration options as opposed to
> library
> settings. for example $PATH_TO_FOO is something that the local admin
> might want to change.
>
> so if most of the utils.pm functions are going into Nagios::Plugin, my
> thinking was that the other stuff could be incorporated into this
> scheme.
I never saw the point of $PATH_TO_FOO variables. I would just call
system() without the full path, no?
Otherwise, if we have this ini configuration file, we could have a
stanza like:
[main]
path_to_rpcinfo=/usr/sbin/rpcinfo
path_to_lmstat=
path_to_smbclient=/usr/bin/smbclient
path_to_mailq=/usr/bin/mailq
path_to_qmail_qstat=
Values added by configure, of course.
I've just thought, if this ini file is created by the nagios-
plugins ./configure, how does Nagios::Plugin know where it resides?
Would it have to check various possible locations?
Ton
http://www.altinity.com
T: +44 (0)870 787 9243
F: +44 (0)845 280 1725
Skype: tonvoon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nagios-plugins.org/archive/devel/attachments/20061018/f109da50/attachment.html>
More information about the Devel
mailing list