--opJtzjQTFsWo+cga
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Feb 21, 2006 at 04:46:10PM +0100, Marc Haber wrote:
> > At run-time, I'd say.
>=20
> Even better, one would have to worry about input processing though.
i think this isn't a big concern... if you look at the
global_command_prefix dpatch[1] (which has been forwarded
to ethan, and i believe committed), you can see that adding
another config file option is basically as simple as adding
another else if(strncmp(...)) do_something.
furthermore, i would strongly advise against hard-coding the location
with #ifdef's. currently in debian the command file for nagios 1.x and
nagios 2.x resides in different directories[2]. if we hard coded the
chroot dir, we could either (a) only support one version of nagios
with this feature or (b) have to provide two seperate binaries
for only this purpose.
sean
[1] dpatch is a popular system for tracking debian-specific patches to
upstream source.
[2] perhaps they should be in the same dir, but it does show the lack of
flexibility provided by this route.
--opJtzjQTFsWo+cga
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD+3zrynjLPm522B0RAo7sAJsGAr1LYKc6MgKm57FpEv47WWuiCACfRc1y
CHVoDU8NvzFiMJaFwMZlhjg=
=8ugO
-----END PGP SIGNATURE-----
--opJtzjQTFsWo+cga--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]