smistrip(1) [debian man page]

smistrip(1)							     SMI Tools							       smistrip(1)

NAME

       smistrip - extract MIB or PIB modules from text files, like RFCs or I-Ds

SYNOPSIS

       smistrip [ -Vhn ] [ -d dir ] [ -m module ] [ file(s) ]

DESCRIPTION

       The  smistrip program is used to extract MIB and PIB module files from ASCII documents like RFCs or Internet Drafts. Modules are identified
       by a starting ASN.1 DEFINITIONS clause and the matching END clause. The output is written to files named by the modules' names.

OPTIONS

       -V     Show the smistrip version and exit.

       -h     Show a help text and exit.

       -n     Print only what would be extracted, but do not write any output file.

       -d dir Write module file(s) to directory dir instead of the current working directory.

       -m module
	      Extract only the module module instead of all modules found in the input file(s).

       file(s)
	      The input text file(s) from which modules will be extracted. If no file is given, input is read from stdin.

       Note that smistrip tries to be smart about locating module start and end, detecting page breaks and blank lines near page breaks.  It  also
       tries  to cut off blank prefixing columns from all lines of a modules. However, there might by documents that cannot be parsed correctly by
       smistrip and probably produce incorrect output.	You might consider to use smilint on every extracted module file to check its  syntactical
       correctness.

EXAMPLE

       This example extracts only the module IPV6-MIB from the file rfc2465 and writes it to the directory /usr/local/tmp.
	 $ smistrip -d /usr/local/tmp -m IPV6-MIB rfc2465

SEE ALSO

       The libsmi(3) project is documented at http://www.ibr.cs.tu-bs.de/projects/libsmi/.

       smilint(1)

AUTHOR

       (C) 1999-2004 F. Strauss, TU Braunschweig, Germany <strauss@ibr.cs.tu-bs.de>
       (C) 2002 M. Bunkus, TU Braunschweig, Germany <bunkus@ibr.cs.tu-bs.de>
       and contributions by many other people.

IBR
								  August 10, 2004						       smistrip(1)

smidiff(1)							     SMI Tools								smidiff(1)

NAME

       smidiff - check differences between a pair of SMI or SPPI modules

SYNOPSIS

       smidiff [ -Vhsm ] [ -c file ] [ -l level ] [ -i error-pattern ] [ -p module ] oldmodule newmodule

DESCRIPTION

       The  smidiff  program  is  used to check differences between a pair of SMI MIB modules or SPPI PIB modules.  E.g., it can be used to detect
       changes in updated MIB modules that can cause interoperability problems with existing implementations. SMIv1/v2 and SPPI style MIB/PIB mod-
       ules are supported.

       Note that conformance statements are currently not checked.

       Messages describing the differences are written to the standard output channel while error and warning messages generated by the parser are
       written to the standard error channel.

OPTIONS

       -V, --version
	      Show the smidump version and exit.

       -h, --help
	      Show a help text and exit.

       -s, --severity
	      Show the error severity in brackets before error messages.

       -m, --error-names
	      Show the error names in braces before error messages.

       -c file, --config=file
	      Read file instead of any other (global and user) configuration file.

       -p module, --preload=module
	      Preload the module module before reading the main module(s). This may be helpful if an incomplete main module misses to import  some
	      definitions.

       -l level, --level=level
	      Report errors and warnings up to the given severity level. See the smilint(1) manual page for a description of the error levels. The
	      default error level is 3.

       -i prefix, --ignore=prefix
	      Ignore all errors that have a tag which matches prefix.

       oldmodule
	      The original module.

       newmodule
	      The updated module.

       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
       smi_config(3) for more details.

SEE ALSO

       The libsmi(3) project is documented at http://www.ibr.cs.tu-bs.de/projects/libsmi/.

AUTHOR

       (C) 2001 T. Klie, TU Braunschweig, Germany <tklie@ibr.cs.tu-bs.de>
       (C) 2001 J. Schoenwaelder, TU Braunschweig, Germany <schoenw@ibr.cs.tu-bs.de>
       and contributions by many other people.

IBR
								  August 10, 2004							smidiff(1)