smilint.html-lang=de.htm

libsmi的使用手册及网站

</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="21%"></td>
<td width="77%"><p>Preload the module <i>module</i> before reading the main
module(s). This may be helpful if an incomplete main module misses
to import some definitions.</p></td>
</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%"><p><b>-l</b><i>level</i><b>, --level=</b><i>level</i></p></td>
</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="21%"></td>
<td width="77%"><p>Report errors and warnings up to the given severity
<i>level</i>. See below for a description of the error levels. The
default error level is 3.</p></td>
</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%"><p><b>-i</b><i>prefix</i><b>, --ignore=</b><i>prefix</i></p></td>
</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="21%"></td>
<td width="77%"><p>Ignore all errors that have a tag which matches <i>prefix</i>. A
list of error tags can be retrieved by calling smilint with the -e
option.</p></td>
</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%"><p><i>module(s)</i></p></td>
</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="21%"></td>
<td width="77%"><p>These are the modules to be checked. If a module argument
represents a path name (identified by containing at least one dot
or slash character), this is assumed to be the exact file to read.
Otherwise, if a module is identified by its plain module name, it
is searched according to libsmi internal rules. See
<b>smi_config(3)</b> for more details.</p></td>
</tr></table>
<a name="ERROR AND WARNING LEVELS"></a><h2>ERROR AND WARNING LEVELS</h2>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%"><p>All generated error and warning messages have an associated
severity level. The actual severity levels are:</p></td>
</tr></table>
<table width="100%" border="0" rules="none" frame="void" cols="3" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%"><p>0</p></td>
<td width="83%"><p>Internal error, no recovery possible. Examples are memory
allocation failures. Errors of this level usually cause the
application to abort.</p></td>
</tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%"><p>1</p></td>
<td width="83%"><p>Major SMI/SPPI error, recovery somehow possible but may lead to
severe problems. Examples are lexically unexpected characters or
unknown keywords. Errors of this kind usually lead to follow-on
errors.</p></td>
</tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%"><p>2</p></td>
<td width="83%"><p>SMI/SPPI error which is probably tolerated by some
implementations. Examples are MIB/PIB modules which mix constructs
from different SMI/SPPI versions.</p></td>
</tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%"><p>3</p></td>
<td width="83%"><p>SMI/SPPI error which is likely tolerated by many
implementations. Examples are misplaced SMIv2 MODULE-IDENTITY
invocations or SMIv2 textual conventions derived from other textual
conventions.</p></td>
</tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%"><p>4</p></td>
<td width="83%"><p>Something which is not strictly an error but which is
recommended to be changed. Warnings of this level are usually
considered during MIB reviews.</p></td>
</tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%"><p>5</p></td>
<td width="83%"><p>Something that is basically correct but might be problematic in
certain environments or usage scenarios. Examples are warnings that
identifiers only differ in case or that type definitions are not
used within the defining module.</p></td>
</tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%"><p>6</p></td>
<td width="83%"><p>Messages of this level are auxiliary notices. Examples are
messages that point to a previous definition in case of a
redefinition.</p></td>
</tr>
</table>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%"><p>Higher levels are currently not used and lead to the same
effects as level 6 does. Note that errors up to level 3 are errors
violating the specifications and must be fixed by the responsible
author. The warnings generated with level 4 should be considered
during normal MIB/PIB reviews.</p></td>
</tr></table>
<a name="EXAMPLE"></a><h2>EXAMPLE</h2>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%">
<p>This example checks the file RMON2-MIB in the current directory
(note that the &#8216;./&#8217; prefix ensures this). The error
level is raised to 6 and warnings that claim about identifier names
that exceed a length of 32 characters are suppressed.</p>
<pre>
  $ smilint -l 6 -i namelength-32 ./RMON2-MIB
  ./RMON2-MIB:3935: unexpected type restriction
  ./RMON2-MIB:3936: unexpected type restriction
  ./RMON2-MIB:3937: unexpected type restriction
  ./RMON2-MIB:3938: unexpected type restriction
  ./RMON2-MIB:3939: unexpected type restriction
  ./RMON2-MIB:3940: unexpected type restriction
  ./RMON2-MIB:4164: scalar object must not have a &#8216;read-create&#8217; access value

</pre>
</td>
</tr></table>
<a name="SEE ALSO"></a><h2>SEE ALSO</h2>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%"><p>The <b>libsmi</b>(3) project is documented at <b>http:
//www.ibr.cs.tu-bs.de/projects/libsmi/</b>. Other commonly used MIB
checkers are <b>mosy</b>(1) and <b>smicng</b>(1).</p></td>
</tr></table>
<a name="AUTHORS"></a><h2>AUTHORS</h2>
<table width="100%" border="0" rules="none" frame="void" cols="2" cellspacing="0" cellpadding="0"><tr valign="top" align="left">
<td width="10%"></td>
<td width="89%"><p>(C) 1999-2004 F. Strauss, TU Braunschweig, Germany
&lt;[e-mail]&gt;<br>
(C) 1999-2002 J. Schoenwaelder, TU Braunschweig, Germany
&lt;[e-mail]&gt;<br>
(C) 2002-2003 J. Schoenwaelder, University of Osnabrueck,
Germany<br>
(C) 2003-2004 J. Schoenwaelder, International University Bremen,
Germany<br>
(C) 2001-2002 T. Klie, TU Braunschweig, Germany
&lt;[e-mail]&gt;<br>
(C) 2002 M. Bunkus, TU Braunschweig, Germany
&lt;[e-mail]&gt;<br>
and contributions by many other people.</p></td>
</tr></table>
</body>
</html>
</body>
</html>