On Wed, 2005-01-05 at 14:45, Magnus Fromreide wrote: > To further mess things up there is a function called setPerrorstatus in > ucd-snmp/errormib.c but since that isn't a mandatory module I think it is a > bug to depend on it at other places.
Agreed. > I think the big question is: > > Should agent/extend and apps/snmptrapd_handlers who depend on > utilities/execute > also depend on ucd-snmp/errormib No. Anything "core" that's currently in a MIB-specific file (and hence compiled into libnetsnmpmibs) should probably be moved into one of the utility files (and hence get compiled into libnetsnmpagent) > or shold the updating of that table be an > issue for the ucd-snmp module so that utilities/execute should avoid > depending on it? One possibility would be for setPerrorstatus (a core utility) to make use of a suitable callback to update the errormib table (an optional mib module). If the errormib module hadn't been initialised, then that callback would be empty. Otherwise it could call the appropriate routines. Much as we currently do with VACM checking, or generating traps. Dave ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
