On Jan 18, 2008 3:45 PM, Dave Shield <[EMAIL PROTECTED]> wrote:
> On 18/01/2008, Nathan Schrenk <[EMAIL PROTECTED]> wrote:
> > there is no way to
> > specify the engineID exactly. I'd like to be able to configure the
> engineID
> > using a command that just takes the hex-encoded raw engineID, similar to
> the
> > oldEngineID command.
>
> Maybe I'm being thick here, but why can't you just use the "oldEngineID"
> directive? What is the difference between this and your proposed new
> "exactEngineID"?
I'd like to preserve the behavior of snmpd with regard to resetting
engineBoots when engineID changes. I imagine that my configuration
application will write an exactEngineID command into /etc/snmp/snmpd.conf
and let snmpd manage engineBoots and oldEngineID in
${persistentDir}/snmpd.conf. This will allow snmpd to reset engineBoots
when engineID changes, which it would not do if I were to just use
oldEngineID.
Nathan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
