I inserted ### before the "perl do" line in each copy of snmpd.conf that had
it. The behavior did not change, i.e. it still timed out as before. (Also
the subagent still appears to function.) I forgot to mention, when I do a
getnext on netSnmp.1.8 I get an additional line that says
Connection from <UNKNOWN>
before it jumps to our private subtree; this does not appear except when I
jump out of netSnmp subtree; but I do not believe that behavior has changed
either.
Thanks,
Larry Dickson
On 2/11/08, Dave Shield <[EMAIL PROTECTED]> wrote:
>
> On 11/02/2008, Larry Dickson <[EMAIL PROTECTED]> wrote:
> > Apparently we have no extend, etc, entries, though there's a "perl do";
> here
> > is the full text (excluding comments and blank lines) of the 3
> snmpd.conf
> > files I found on the system (=== lines are my commentary):
>
>
> > === Contents of (recently created) /etc/snmp/snmpd.conf
> > #version 1
> > trapsink 192.168.1.122
> > rocommunity public
> > rwcommunity private
> > syscontact Larry Dickson
> > syslocation Cutting Edge
> > master agentx
> > perl do /etc/edgeware-subagent.pl
>
> Hmmmm....
>
> What happens if you comment out the "perl" line,
> and restart the agent? Can you get a response to
>
> snmpgetnext .... netSnmp.1.3
>
> then?
>
> (I realise that this may well disable your subagent, but it's worth
> checking whether this is related to the hanging problem or not).
>
> Dave
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
