On 06/12/2007, Giuseppe Modugno <[EMAIL PROTECTED]> wrote:
> So the question is: what are the main advantages to use dlmod or AgentX
> approach against the external stand-alone application that reads from command
> line parameters and writes to standard output?
Three main advantages:
a) The "pass" mechanism will invoke a separate sub-process for every
incoming request. (Or rather, for each relevant varbind in every
incoming request).
Both dlmod and AgentX have a single process running all the
time, So they are typically more efficient - particularly on a
busy or heavily loaded system.
b) The "pass" script has to deal with analysing the requested OIDs
and determining the required value. This is not too bad with GET
requests, but can be non-trivial to get right for GETNEXT.
Both dlmod and AgentX can use the helper handlers to take
care of most of this processing automatically.
c) The "pass" mechanism doesn't handle failed SET requests very well.
There's no facility for validating or reversing a SET varbind.
Both dlmod and AgentX can handle the full SET processing.
The main difference between dlmod and AgentX is that dlmod only works
with the Net-SNMP agent, and AgentX is an Internet standard (which should
work with a wide variety of vendors' agents).
Dave
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders