I am writing a management module that is part of a larger application.
The structure is such that my module may be instructed to shut down and
possibly restart multiple times during the lifetime of the parent app.
Also during these transitions, the parameters needed for any SNMP
sessions I conduct may change.
Here's my problem: init_snmp() is internally guarded against multiple
invocations. So if I call snmp_shutdown() as part of my transition to
quiescence (because my module may or may not be unloaded from memory
between activity sessions), parts of the SNMP environment will be
invalidated that will not be re-initialized by subsequent calls to
init_snmp().
I did search the list archives, and while I saw this situation
mentioned, I did not find a solution. Is this covered by a Best
Practices document somewhere? Or perhaps a list member has confronted
this and can offer some guidance?
Any and all clues appreciated, and thanks for your time.
--
Roy M. Silvernail is [EMAIL PROTECTED], and you're not
"Angry men in combat fatigues talking to God on a two-way
radio and muttering incoherent slogans about freedom are
eventually going to provide us with a great deal of
entertainment." - George Carlin
CRM114->procmail->/dev/null->bliss
http://www.rant-central.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
