|
|
1.1 root 1: .TH MOSY 1 "15 May 1988"
2: .\" $Header: /f/osi/others/mosy/RCS/mosy.1,v 7.0 89/11/23 22:00:37 mrose Rel $
3: .\"
4: .\"
5: .\" $Log: mosy.1,v $
6: .\" Revision 7.0 89/11/23 22:00:37 mrose
7: .\" Release 6.0
8: .\"
9: .SH NAME
10: mosy - Managed Object Syntax-compiler (yacc-based)
11: .SH SYNOPSIS
12: .in +.5i
13: .ti -.5i
14: .B mosy
15: \%[\-o\0module.defs]
16: \%[\-s]
17: \fImodule.my\fR
18: .in -.5i
19: .SH DESCRIPTION
20: The \fImosy\fR program reads a description of a \fImanaged objects\fR
21: module and produces a simple ascii file containing equivalent definitions.
22: This file is meant to be read as configuration data by a network
23: management program.
24: .PP
25: The `\-o' switch sets the name of the output file,
26: which is normally derived from the name of the input file.
27: The distinguished file \*(lq\-\*(rq can be used to force the use of the
28: standard output.
29: .PP
30: Normally, \fImosy\fR prints the name of each object, identifier, or type
31: as it works.
32: The `\-s' switch disables this behavior.
33: .SH "SEE ALSO"
34: pepy(1),
35: .br
36: \fIThe ISO Development Environment: User's Manual\fR,
37: .SH AUTHOR
38: Marshall T. Rose,
39: NYSERNet Inc.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.