Instead of starting snmpd with D nstAgentSubagentObject you want to pass that command-line option to your subagent when you start it In the tutorial it suggests starting the subagent with the following command: % . /mysubagent & To enable the more debug messages, try starting it with the following command instead: % . /mysubagent -D nstAgentSubagentObject If I remember correctly, that should print out the debug output to the console.
You can combine it with the L option if you'd prefer it written to a file.
Instead of starting snmpd with -D nstAgentSubagentObject you want to pass that command-line option to your subagent when you start it. In the tutorial it suggests starting the subagent with the following command: % . /mysubagent & To enable the more debug messages, try starting it with the following command instead: % .
/mysubagent -D nstAgentSubagentObject If I remember correctly, that should print out the debug output to the console. You can combine it with the -L option if you'd prefer it written to a file.
FYI, you can also put the following into a snmp. Conf file and twiddle the options there too: debugTokens nstAgentSubagentObject doDebugging 1 But, the other answer is spot on: you need to turn on debugging where the code will be hit, which is in the subagent (the snmp. Conf file will be read by both).
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.