Hello Dave, > > Have you tried 5.3? >
I have to admit that I did not because it takes me two or three days to upgrade from one version to another. This 'feature' is present from the begining of the snmp story for our project; from version 5.1.1 (I wrote wrong version in first mail). At least I strongly beleive so... because we have had a lot of other problems... However, the toughest thing here is that I cannot use debug macros (not enough flash space at embeded system-I have to strip binaries), remote debugging is hard (when I stop gdb at host system, gdbserver kill the proccess at remote embeded). It seems I'm looking for the needle in the haystack... But now I'm thinking... First we started with netsnmp version 5.1.1, the next logical upgrade will be to 5.3? (In the mean time we upgraded to 5.2.1.rc2, followed now by 5.2.2...) We actually first use unstable, advanced version 5.1.1 and then downgraded to 5.2.1.rc2? So, are there any relevant differences between 5.1.X version compared to 5.2.X that could carry out 'dead' behavior of the master? Are there any similar feature like name of persistent files I wrote about it? What about libraries that are the same to all agents and master? (libraries are built first for the master and then replaced with subagent one) Thank you in advance, Igor G. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
