Libsmi November 2007

libsmi@ibr.cs.tu-bs.de

3 participants
4 discussions

Messages on Dup Imports
by David T. Perkins 16 Nov '07

16 Nov '07

HI, In cleaning up a MIb module, it had the following imports: IMPORTS OBJECT-TYPE FROM SNMPv2-SMI OBJECT-TYPE, IpAddress, MODULE-IDENTITY, enterprises FROM SNMPv2-SMI DisplayString, TruthValue FROM SNMPv2-TC; With a level 5 or greater, smilint generated the warning: warning: identifier `OBJECT-TYPE' imported from module `SNMPv2-SMI' is never used This is misleading. I was expecting the following two warnings: 1) duplicate definition of "OBJECT-TYPE" 2) all of the items from a module must be imported together Regards, /david t. perkins

2 3

Missing warning
by David T. Perkins 07 Nov '07

07 Nov '07

HI, I'm doing some cleanups of sme MIB modules. In them are many examples of tables that have a RowStatus column (with no restriction of values) and have MAX-ACCESS of "read-write" on the columns. I was expecting to see a warning that "read-create" should have been used instead of "read-write". If this warning is presently generated, I suggest that it be added. Regards, /david t. perkins

2 2

Bug in pattern generation for ranges
by Arndt Jonasson 06 Nov '07

06 Nov '07

In the file tools/fortopat.c is this code: for (range = smiRange, lp = 0; range; range = smiGetNextRange(range)) { lengths[lp++] = smiRange->minValue.value.unsigned32; lengths[lp++] = smiRange->maxValue.value.unsigned32; This ought to be for (range = smiRange, lp = 0; range; range = smiGetNextRange(range)) { lengths[lp++] = range->minValue.value.unsigned32; lengths[lp++] = range->maxValue.value.unsigned32; or the ranges after the first one will effectively be ignored.

2 3

Some cleanups on the package
by David T. Perkins 01 Nov '07

01 Nov '07

HI, I just did a checkout through subversion and found a few items that would be nice if they were cleaned up. These include: 1) the README file leaves out a few pieces of info that would have saved me from having to figure them out. These include: a) it doesn't mention that you have to run script autogen.sh to generate the configure script b) the manifest is out of date, since it doesn't include autogen.sh nor smi.conf-example c) it would be helpful to list the files that were to be copied for "make install", and the source and dest directories d) More info needs to be given about interesting options to set for the configure script. (I didn't use the prefix option, and then make install failed (since I don't have admin capabilities on the system). I then when back and used --prefix=$HOME on configure, then rebuilt, then installed.) I'm not sure yet if there are "features" that I need to turn on or off. e) There is a passing reference to the smi_config(3) man page. A little more info is needed, with some suggestions for setting up a local (.smirc) and system wide (smi.conf) files. 2) The "make check" failed. It appears that the expected results were not updated after libsmi was changed. And there might be a bug or two. Someone should check. 3) I looks like the list of unversioned files to ignore should be updated so that svn doesn't give bogus warnings. 4) Note that on the WEB pages, it would be nice if there was a style sheet for printers so that when, say, a man page was printed, the left side nav <div> was not shown. Regards, /david t. perkins

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Libsmi November 2007