Robert Story wrote:
On Tue, 22 Feb 2005 12:53:09 -0500 Rob wrote:
RK> >Ok. I have a theory now. Try running the agent with the 'table_set' debug
RK> >token, and send me the debug output after the SIGHUP signal is sent.
RK> >
RK> OK let's see if I did this correctly:
RK>
RK> /usr/local/sbin/snmpd -
On Tue, 22 Feb 2005 12:53:09 -0500 Rob wrote:
RK> >Ok. I have a theory now. Try running the agent with the 'table_set' debug
RK> >token, and send me the debug output after the SIGHUP signal is sent.
RK> >
RK> OK let's see if I did this correctly:
RK>
RK> /usr/local/sbin/snmpd -Dtable_set
RK>
RK>
Robert Story wrote:
On Tue, 22 Feb 2005 09:33:57 -0500 Rob wrote:
RK> Yes, it was initially generated by mib2c (from net-snmp 5.1.2 package)
RK> using mib2c.create-dataset.conf.
Ok. I have a theory now. Try running the agent with the 'table_set' debug
token, and send me the debug output after the
On Tue, 22 Feb 2005 09:33:57 -0500 Rob wrote:
RK> Yes, it was initially generated by mib2c (from net-snmp 5.1.2 package)
RK> using mib2c.create-dataset.conf.
Ok. I have a theory now. Try running the agent with the 'table_set' debug
token, and send me the debug output after the SIGHUP signal is se
On Thu, 17 Feb 2005 14:54:57 -0500 Rob wrote:
RK> It's coming from our custom MIB. From our MIB and structure file:
Ok, but you didn't answer my question:
RK> >[Was mppLibraryVersionTable] generated by mib2c? If so, which conf file?
Yes, it was initially generated by mib2c (from net-snmp 5.1.2 p
