Re: [Nagios-devel] vanished bug numbers in the nagios mantis tracker
Posted: Tue Aug 07, 2012 4:41 pm
On 08/07/2012 03:21 PM, Andreas Ericsson wrote:
> [...] Each module gets to keep its own data and Nagios doesn't need to
> know anything at all about it (although it would be neat if it could
> issue a callback and get a key/value vector when printing status data).
[...]
> It would ofcourse be nifty if modules *did* know about each other's
> data, assuming they explicitly request it, but that's not what you're
> talking about so let's ignore that for now.
FWIW (and not that I've ever coded such a thing myself), if two modules
would *want* to share data, all they would need beyond the OS' shared
memory support would be unique module IDs, a means to coordinate startup
priority (so that the module that actually *creates* the shared memory
can do so before the "user" modules ask for it), and a means of
user-module---to-nagios-core---to-creator-module "hey creator module,
hand me the necessary access data!" requests. Assuming that there are no
"malevolent" modules you have to protect the same data against, that is.
One thing that needs to be pinpointed for your object IDs, however,
would be their (guaranteed) lifetime. Should they be persisted until the
next reload, restart, or even across config changes (say, a host getting
renamed)? After all, saying that "it's the module's business what data
to attach to the ID, I don't care" maximizes the chance that someone'll
write a module whose extra data then suddenly has a legitimate *need* to
be persisted.
Kind regards,
J. Bern
--=20
*NEU* - NEC IT-Infrastruktur-Produkte im :
Server--Storage--Virtualisierung--Management SW--Passion for Performance
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> [...] Each module gets to keep its own data and Nagios doesn't need to
> know anything at all about it (although it would be neat if it could
> issue a callback and get a key/value vector when printing status data).
[...]
> It would ofcourse be nifty if modules *did* know about each other's
> data, assuming they explicitly request it, but that's not what you're
> talking about so let's ignore that for now.
FWIW (and not that I've ever coded such a thing myself), if two modules
would *want* to share data, all they would need beyond the OS' shared
memory support would be unique module IDs, a means to coordinate startup
priority (so that the module that actually *creates* the shared memory
can do so before the "user" modules ask for it), and a means of
user-module---to-nagios-core---to-creator-module "hey creator module,
hand me the necessary access data!" requests. Assuming that there are no
"malevolent" modules you have to protect the same data against, that is.
One thing that needs to be pinpointed for your object IDs, however,
would be their (guaranteed) lifetime. Should they be persisted until the
next reload, restart, or even across config changes (say, a host getting
renamed)? After all, saying that "it's the module's business what data
to attach to the ID, I don't care" maximizes the chance that someone'll
write a module whose extra data then suddenly has a legitimate *need* to
be persisted.
Kind regards,
J. Bern
--=20
*NEU* - NEC IT-Infrastruktur-Produkte im :
Server--Storage--Virtualisierung--Management SW--Passion for Performance
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]