[Nagiosplug-devel] Kickoff for 1.5

Voon, Ton Ton.Voon at egg.com
Tue Mar 29 00:41:24 CEST 2005

Sorry guys, haven't been staying on top of these emails.

I think it is a great idea to separate the suid plugins, if only because
they have to be installed differently (as root, rather than as a nagios
or own user). I don't think their support *should* be any different -
after all that was part of the discussion we had prior to the 1.4
release and I think we took it on that this was now part of our core.
However, by having a separate directory, it is clear they are
"different". So I'd advocate keeping them in by default.

Stanley, do you want to move the suid stuff into a separate directory?
(suid/? plugins-suid/? plugins-root/?) Will need to make some changes to
the makefile.am at the top level.

As to the other things that were discussed for 1.5, will need to start
summarising and seeing who wants to pick up which tasks. I can track
allocation via email, unless SF has some better tools for doing it.


-----Original Message-----
From: nagiosplug-devel-admin at lists.sourceforge.net
[mailto:nagiosplug-devel-admin at lists.sourceforge.net] On Behalf Of
Stanley Hopcroft
Sent: 29 March 2005 07:57
To: NagiosPlug Devel
Subject: Re: [Nagiosplug-devel] Kickoff for 1.5

Dear Folks,

The only comment I have about 1.5 is suggesting the separation of the
suid C plugins from the non-suid plugins.

I think this is necessary because apart from the weaknesses in the
implementations of the the suid plugins (check_dhcp, check_smart_*),
testing becomes much more difficult on non core platforms.

I do not have root access on

HPUX     - any version
Solaris  - "
OS-X     - "
AIX      - "

and I cannot imagine getting such access to any but a subset (at best
AIX and Solaris).

These plugins then are unlikely to have the same degree of testing that
the others have and therefore are unlikely to perform as well.

Putting them in their own optional build directory (say /suid) with a
README like that for /contrib may be beneficial in

1 stopping build failures caused by these plugins

2 lowering expectations about the performance of these plugins.

Yours sincerely.


Egg is a trading name of the Egg group of companies which includes: Egg plc
(reg no 2448340), Egg Financial Products ltd (reg no 3319027), Egg
International ltd (reg no 4059266), Egg Financial Intermediation ltd (reg
no 382828), Egg Investments ltd (reg no 3403963) and Egg Banking plc (reg
no 2999842.  Egg Investments Ltd, Egg Banking plc and Egg Financial
Intermediation Ltd are authorised and regulated by the Financial Services
Authority (FSA) and are entered in the FSA register under numbers 190518,
205621 and 309551 respectively. These members of the Egg group are
registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA.    This e-mail is confidential and for
use by the addressee only.  If you are not the intended recipient of this
e-mail and have received it in error, please return the message to the
sender by replying to it and then delete it from your mailbox.  Internet
e-mails are not necessarily secure. The Egg group of companies do not
accept responsibility for changes made to this message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by the Egg group of companies in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
This communication does not create or modify any contract.

More information about the Devel mailing list