On 27/04/07, Reza Salehi <[EMAIL PROTECTED]> wrote:
> About this part of your E-mail:
>
> >>>>>>Normally, this buffer would be updated automatically
> as part of the normal operation of the subsystem.
>
> Could you give an example of this? Are they using timer for
> updating the buffer?
> What do you mean by subsystem and normal operation?
Take a step back, and think about what SNMP is for.
It's all about "management" - monitoring and configuring
some form of computer behaviour.
Now this may come as a surprise to a large slice of
the working population, but "management" is not in itself
an important activity - it's (at best) a necessary evil to
support the real work.
That's true of human organisations, and it's equally true
of computer systems. By "subsystem", I mean the bit
of the computer that actually does this work - be that a
piece of software (e.g. a web server or database server),
or some hardware (e.g. a network interface, or disk drive).
That (software or hardware) is the reason for having the
computer in the first place - the "normal operation" of
this subsystem.
SNMP is just there to check that this subsystem is working
correctly, and adjust things if appropriate.
OK - that's covered "normal operation of the subsystem".
What about automatic updating of the watched buffer?
The real advantage of this watched buffer approach is where
the SNMP component is embedded within the main application
(e.g. a subagent thread within a web server process).
This web server might be configured with a maximum number
of simultaneous connections, so it would need to have a
variable to hold this value, and another to hold the current
number of connections:
int max_conn;
int curr_conn;
That's not something special for SNMP - it's part of the
"normal operation" of the web server. But an embedded
SNMP subagent can make use of these same variables.
It doesn't need any special code to retrieve these two values,
it can simply invoke suitable:
"netsnmp_register_int_instance( ... &max_conn);"
and
"netsnmp_register_int_instance( ... &curr_conn);"
calls, and the SNMP helpers will report the current
values of these two variables.
As connections are made (and dropped) to the web server,
the value of 'curr_count' will be updated automatically
(because that's what this variable was for in the first place).
That's what I mean by
"... [a] buffer [being] updated automatically
as part of the normal operation of the subsystem."
OK?
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
