Hi Dave,
 thanks for the quick response. Yes, I did mean snmp-notification-mib.

I guess I am trying to get the correct "workflow". I understand that the mib2c 
will not generate the finished code but now that we have cranked the handle 
once with snmpNotifyFilterTable files, do we simply treat them (from now on) as 
files to be hand-coded? Or, do we somehow feed back corrections into the 
generator and then re-run mib2c? Ideally, there would be hand-coded 
functionality specific to the tables and this would be separate to the 
auto-generated code, so that if generic problems were found, the scripts could 
be re-run without losing hand-crafted edits.

With each suite of software delivered (say net-snmp-5.5) both the mib2c scripts 
and the already-generated files (snmpNotifyFilterTable.c, etc) are provided. 
Are the mib2c scripts purely for the benefit of creating new user-defined 
tables? As I said previously, I still can't see exactly what commands would 
have been run to re-generate the files.

Regards,
Adam.




> -----Original Message-----
> From: dave.shi...@googlemail.com 
> [mailto:dave.shi...@googlemail.com] On Behalf Of Dave Shield
> Sent: Wednesday, January 13, 2010 1:43 PM
> To: Lewis Adam-VNQM87
> Cc: net-snmp-users@lists.sourceforge.net
> Subject: Re: mib2c generation of snmpNotifyFilterTable code
> 
> 2010/1/13 Lewis Adam-VNQM87 <vnq...@motorola.com>:
> > Looking at the files that combine to provide support for the
> > snmpNotifyFilterTable:
> >
> >  agent\mibgroup\notification\snmpNotifyFilterTable.c
> >  agent\mibgroup\notification\snmpNotifyFilterTable_data_access.c
> >  agent\mibgroup\notification\snmpNotifyFilterTable_interface.c
> >  etc.
> 
> I presume you mean "snmp-notification-mib" rather than "notification"
> The FilterTable has been implemented separately from the 
> basic NotifyTable, and the FilterProfileTable
> 
> 
> > I can see that these files are generated by mib2c but what 
> I can't see 
> > are the exact commands (presumably in a makefile somewhere) that 
> > generate these files.
> 
> From the style of the filenames, this looks like an MfD-based 
> implementation.
> 
> 
> > Is the code generation completely generic or has there been some 
> > customisation specifically for snmpNotifyFilterTable?
> 
> Almost *every* MIB implementation will include specific customisation.
> There are very few MIBs where mib2c will generate fully-working code.
> 
> The purpose of mib2c is to produce a *template* for a MIB 
> implementation,
> not to generate the final code automatically.   It only knows 
> about the
> syntax of the MIB objects - it can't possible handle the semantics
> of these objects.   That's what the (human) coder is for.
> 
> 
> > I think I have found a problem (setting rowStatus to createAndWait 
> > should leave it in notInService state rather than 
> createAndWait state) 
> > and I wanted to know how best to apply a fix.
> 
> I think you're probably right.
> The routine snmpNotifyFilterTable_check_dependencies()
> handles the mapping of createAndGo into Active, but doesn't 
> do anything with createAndWait vs notInService/notReady
> 
> 
> Feel free to submit a patch to the project tracker.
> 
> Dave
> 

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
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

Reply via email to