[Pkg-nagios-devel] final changes for upstream release
seanius at debian.org
Tue Feb 7 22:07:25 UTC 2006
so, apparently 2.0 is out the door.
i'd like to make 3 rather superficial last-minute changes,
and discuss one potentially larger change, and then send
things on their way:
- change in configuration file naming. i'd like to change
i think keeping nagios2 in the name is helpful to
identify it as something we put there (regardless of
whether or not anything actually makes use of it it's
informative), but for tab-key preservation etc it
makes the most sense to me to but the most significant
bits first hence the switch of ordering.
- man page for nagios2 and nagios2stats. i'll get started on this.
- a brief general description of our configuration methodology
- a change in the recommended procedure for manually configuring
external checks. after setting check_external_commands=1:
dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios2/rw
however we have to make a slight change in our postinsts to
not overwrite this. instead of:
install -d -onagios -gnagios -m750 /var/lib/nagios2/rw
we'd just do
chown nagios /var/lib/nagios2/rw
and we'd have to make sure the dir is be shipped in the nagios2-common
deb as root:www-data/0700. this way setgid permission changes would
be respected across upgrades, and we wouldn't need to create another
- finally, put in some debconf/maintscript support for the above.
(though defaulting to leaving it off). the trickiest part of this is
that there's a cfg file setting that needs to be changed, which makes
things somewhat complicated. the *wrong* way to do this would be
to edit the file, which is what i think the 1.x packages do. instead
we should split the file out into a seperate ucf-managed file,
and reregister it via ucf every time we change it (thus preventing
nasty unnecessary conffile prompts)
*but* i'd rather not do such a big change before the first upload.
soo.... my proposition is that we go ahead and move the
setting into its own and ucf-managed file in the conf.d dir,
and save the rest for later, which we should then be able
to add in at our leisure without making any impact on existing systems.
so, that's my list of last-minute thoughts on the package. thoughts?
as for timeline... i think it'd be feasible to have something
uploaded in the next 48 hours at the latest, depending on
how controversial my suggestions turn out to be :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-nagios-devel/attachments/20060207/a00af6d3/attachment.pgp
More information about the Pkg-nagios-devel