> NETSNMP_DS_LIB_APPTYPES seems to be the sum of all types of config that is to > be read while > NETSNMP_DS_LIB_APPTYPE seems to be the 'natural' type that is parsed.
Yes - that's right. > but I do agree that I do not understand the exact implications of them. No - neither do I :-) That tends to be what happens when a new feature is first brought into being.... Off the top of my head, things should work as follows: A given application has a "natural" type, and this is basically what is used for the vast majority of config processing. Most config handlers will be registered to use this type (and hence be expected to appear in "type.conf" files), and any persistent information will be saved in another "type.conf" file. The idea of "type:type2" is to allow specific config tokens to legitimately appear in a different "type2.conf" file - probably as well as "type.conf" (though there might be an argument to be made for *just* accepting a particular token in "type2.conf" files). > Oh yes, i think your patch would prevent parsing of agentx tokens in the > agentx.conf file. Yes. That's probably very sensible since this feature doesn't yet work properly! Now that Robert's pointed me in the right direction, I can have another look at this problem. Dave ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
