Hi,
I want to ask a simple query. I have downloaded net-snmp-5.1.1 source code and compiled it to form a snmpd executable for mips linux.
Now can I specify the version of snmp (1,2 or 3) at runtime so that same snmpd file can act as v1, or v2 agent without recompilation? If yes then how and where do I specify the snmp version so that snmpd can read it at runtime? Or is it necessary to recompile the source code if I want to change the snmp version?
Thanks in advance,
-Mayuresh.
Dave Shield <[EMAIL PROTECTED]> wrote:
On Fri, 2005-01-07 at 16:29, Robert Story wrote:
> On Fri, 07 Jan 2005 10:34:45 +0000 Dave wrote:
> DS> It appears that in most cases, the MfD framework effectively splits
> DS> each pass of the "traditional" SET handling model
>
> Yes. The idea is that eventually the agent will use the baby step modes, and a
> helper will be created to map back for the old style modes. That was supposed
> to make it in to 5.2, but didn't. Probably won't make it into 5.3 either.
Hmmm.... I'm not sure I remember that decision. Or even the discussion
that presumably preceded it. And (as you might have guessed!), I don't
think it's a good idea.
I can see the benefits of having this sort of fine-grained framework
available, but the current baby_steps handler seems a sensible way of
providing this. It takes the current (fair ly broad-brush) six-pass
framework, and refines the tasks involved in each one. I've no
problem with that at all.
But to reverse things, and have the 14-pass model of the baby_steps
handler as the fundamental way of working seems both unwise and
unnecessarily complicated.
It would mean that the six existing passes would have to be shoe-horned
into selected steps of the baby_steps framework, despite the tasks
involved being wider than implied by those particular mini-passes.
That introduces unnecessary confusion, IMO.
Not to mention that the current baby_steps framework cannot properly
handle invoking the FREE pass - at least not without contortions to
avoid getting this mixed up with the UNDO and COMMIT passes as well.
I also find this slightly at odds with your comment:
> I'd much rather not add more states. I really think the
> goal should be the simplest state diagram possible.
The existing mod el is significantly simpler than the state
diagram of the baby_steps framework.
What are the benefits of changing the architecture of the agent?
Dave
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
ALL-NEW Yahoo! Messenger - all new features - even more fun!
