2009/5/19 Vinod Nanjaiah vinod_nanja...@mindtree.com:
When control comes to snmp_parse_args, it messes up the argc and argv
parameters and the
program seg faults at a later point when the argv is referenced.
This is the argv that I am using
char com[] = ”public”;
char *argv[] = {, -v, 1,
Hi!
What is a correct way to say we're reached End Of Subtree by subagent
for GETNEXT request?
Most natural way I see - to return error. But it does not look good by
snmpwalk:
NET-SNMP-MIB::netSnmp.2.1.2.0.5.98 = INTEGER: 0
NET-SNMP-MIB::netSnmp.2.1.2.0.5.99 = INTEGER: 0
2009/5/20 Sergey Matveychuk s...@ciam.ru:
What is a correct way to say we're reached End Of Subtree by subagent
for GETNEXT request?
Return the 'endOfMibView' exception - see RFC 2741, section 7.3.2.2.
This should be handled automatically by the subagent framework.
All your MIB module handler
Dave Shield wrote:
2009/5/20 Sergey Matveychuk s...@ciam.ru:
What is a correct way to say we're reached End Of Subtree by subagent
for GETNEXT request?
Return the 'endOfMibView' exception - see RFC 2741, section 7.3.2.2.
This should be handled automatically by the subagent framework.
All
2009/5/20 Sergey Matveychuk se...@yandex-team.ru:
This should be handled automatically by the subagent framework.
All your MIB module handler typically needs to do is return without
setting a value.
I've tried it, but snmpwalk got a timeout:
NET-SNMP-MIB::netSnmp.2.1.2.0.5.98 = INTEGER: 0
string, security name or the two pass phrases).
This is to avoid them being visible in the output of ps or in core dumps.
Untested, but you might want to try setting the first parameter
to be snmpd-proxy. This will suppress the clearing of these
sensitive parameters.
(We could perhaps do
This ia a list of specific bugs that have been fixed, and patches
that have been applied in released versions. Please see the NEWS file for
a summary of the major changes, and the ChangeLog file for a comprehensive
listing of all changes made to the code.
*5.3.3.rc2*
snmplib:
- [PATCH
