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
2009/5/19 Vinod Nanjaiah :
> 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", "-c", com, "172
> From: Vinod Nanjaiah [mailto:vinod_nanja...@mindtree.com]
> Sent: Tuesday, May 19, 2009 3:49 AM
> 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.
I'm not sure, but I thin
Hi,
Has anyone faced any problems in using snmp_parse_args?
This is used in the snmptrap.c file.
I am trying to send trap from an ARM board to a host pc.
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 r
