Re: [Nagios-devel] host_name and service_description examples
Posted: Wed Jun 15, 2005 12:09 pm
--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 15, 2005 at 09:42:56PM +0200, Andreas Ericsson wrote:
> As a module, I believe. The module api lets nagios work similar to gcc;=
=20
> One module can load the config. The core does the work and another=20
> module does the logging (similar to frontend, optimizer and backend).
ah, cool. when i sit down and start seriously looking at nagios2, i'm
sure this will become much more clear. =20
> Notifications is another thing that perhaps ought to be moved out to a=20
> module. It's not strictly necessary on a slave-server sending passive=20
> checks to a master host, and compartmentalizing code is most definitely=
=20
> a Good Thing. Nagios will need to understand
>=20
> include /etc/nagios-modules/*.cfg
like perhaps the already existing "cfg_dir=3D/etc/nagios-modules" ?=20
sean
--6TrnltStXW4iwmi0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFCsIrWynjLPm522B0RAu3gAKCEDorzJYI2uixbyoeW/2m9UOaRcwCcCNEg
VnHKvVNwl1QFs4ERvpByOzM=
=+Y2c
-----END PGP SIGNATURE-----
--6TrnltStXW4iwmi0--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 15, 2005 at 09:42:56PM +0200, Andreas Ericsson wrote:
> As a module, I believe. The module api lets nagios work similar to gcc;=
=20
> One module can load the config. The core does the work and another=20
> module does the logging (similar to frontend, optimizer and backend).
ah, cool. when i sit down and start seriously looking at nagios2, i'm
sure this will become much more clear. =20
> Notifications is another thing that perhaps ought to be moved out to a=20
> module. It's not strictly necessary on a slave-server sending passive=20
> checks to a master host, and compartmentalizing code is most definitely=
=20
> a Good Thing. Nagios will need to understand
>=20
> include /etc/nagios-modules/*.cfg
like perhaps the already existing "cfg_dir=3D/etc/nagios-modules" ?=20
sean
--6TrnltStXW4iwmi0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFCsIrWynjLPm522B0RAu3gAKCEDorzJYI2uixbyoeW/2m9UOaRcwCcCNEg
VnHKvVNwl1QFs4ERvpByOzM=
=+Y2c
-----END PGP SIGNATURE-----
--6TrnltStXW4iwmi0--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]