This is a multi-part message in MIME format.
------_=_NextPart_001_01C64F86.9BBCA1AD
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
After spending some time looking through the
ndomod.c code I have some questions in regards to
the sinkbuf struct.
1. It's my understanding that this is only an in-memory
linked list. Does this not create a potential for lost
events when the broker dies. Should ndomod_sink_buffer_deinit
function maybe write out its contents to disk on module
termination and read in this file on ndomod restart?
What about the case if the module dies erroneously during
standard execution?
2. rather that writing sinkbuf to file, perhaps a backend
data store such as sqlite or berkeleydb could serve as an
additional persistence layer for these events.
I apologize in advance if I've misunderstood the c code and
my assumptions are wrong.
Nicholas Whiting
Network Management Administrator
[email protected]
www.guest-tek.com1-866-509-1010=20
ext 8433
Direct (403) 444-84333
------_=_NextPart_001_01C64F86.9BBCA1AD
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
ndomod.c persistence questions
After spending some time looking through the
ndomod.c code I have some questions in regards to
the sinkbuf struct.
1. It's my understanding that this is only an in-memory
linked list. Does this not create a potential for lost
events when the broker dies. Should ndomod_sink_buffer_deinit
function maybe write out its contents to disk on module
termination and read in this file on ndomod restart?
What about the case if the module dies erroneously during
standard execution?
2. rather that writing sinkbuf to file, perhaps a backend
data store such as sqlite or berkeleydb could serve as an
additional persistence layer for these events.
I apologize in advance if I've misunderstood the c code and
my assumptions are wrong.
Nicholas Whiting
Network Management Administrator
[email protected]
www.guest-tek.com1-866-509-1010
ext 8433
Direct (403) 444-84333
------_=_NextPart_001_01C64F86.9BBCA1AD--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]