On 13 July 2010 15:31, Doroubo Doroubo <doro...@hotmail.com> wrote: > I am running a script to run my application upon boot-up. My script > contains the following: > > ================================ > #!/bin/bash > > export ZSNMPPATH=/zsnmp/sbin > export MIBDIRS=/zsnmp/share/snmp/mibs > export SNMPCONFPATH=/zsnmp/share/snmp:. > export ZSNMPCONFPATH=/zsnmp/share/snmp > export MIBS=+ZANDAR-ARM-MIB > > ./zsnmp_agent& > ================================ > > The zsnmp_agent, which is my application (a subagent) calls via system call > "/zsnmp/sbin/snmpd -x tcp:localhost:4030" to start snmpd.
Why not simply start the master agent first (from within the script), and then start the subagent once this is up and running? It feels somewhat contrary to have the subagent responsible for invoking the master agent. > This resets the syslocation/syscontact that was already saved in > /var/net-snmp/snmpd.conf. I find this weird. When I just call > "/zsnmp/sbin/snmpd -x tcp:localhost:4030", it doesn' affect my saved values. Boggle. I've no idea what might be happening here. There's obviously something strange about the environment set up by your subagent application. All I can suggest is that you try to separate the two, and invoke them independently. If it behaves itself when run by hand, it's more likely to behave when started from the script, rather than by the subagent application. Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
