Hello Fulko, Thank you for the feedback.
Do you mean that we should implement it as a perl sub-agent, or that in general you cannot have more than one "perl do" commands in the snmpd.conf ? thanks Vasilis --- Vasileios Pappas, Ph.D. Research Staff Member IBM TJ Watson Research Center Fulko Hew <[email protected]> wrote on 01/20/2010 12:40:54 PM: > On Wed, Jan 20, 2010 at 8:38 AM, Jens Osterkamp <[email protected] > > wrote: > > Hello everybody, > > we have started to implement the brige mib (RFC 4188) as a perl module. > > Currently implemented are > - dot1dBasePort > - dot1dBasePortIfIndex > - dot1dTpFdbAddress > - dot1dTpFdbPort > - dot1dTpFdbStatus > > We are planning to extend it piece by piece. > > One of the limitations that we have identified so far is that the bridge mib > only represents one but not multiple bridge instances. > > I am attaching the perl code to this email and not submitting a patch to > sf.net as I am not sure on how the perl module could be integrated into net- > snmp. > > Under Linux, the module can be installed by adding > > perl do "/etc/snmp/bridge.pl" > > to /etc/snmp/snmpd.conf. > > Any comments and suggestions are highly appreciated ! > > AFIK the 'do' approach allows only one Perl module to be attached. > While it might be OK for your module, what about all the others. > So I would consider that to be unacceptable, because it is not scalable. > > Fulko ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
