# This is a template for a standard DSAP man page.  
# After you've filled in the necessary fields, 
# delete the lines beginning with "#"
# with a command like: "sed '/^#/d'". 
#
# Use "man -l" to look at your formatted man page before installing it.
#
# However, if you write a man page which describes several routines 
# or commands, you should have a man "page" named after each routine or 
# command.  One will have the actual description in it, the others will
# just include the first with a line like:
# .so man3/malloc.3v
#
# The next line just puts a version number from SCCS in the file.
#
.\" $Name:  $ $Date: 1997/09/30 16:14:04 $
#
# Fill in TITLE in all caps -- SECTION# can be 1 3 3F or 5
#
.TH TITLE SECTION# "$Date: 1997/09/30 16:14:04 $"
#
.SH NAME
#
# For a command manpage, put the command name and brief description next;
# eg,  "ls \- list directory"
# For a set of subroutines, put each subroutine name separated by commas, 
# followed by the brief description.
# eg, "malloc, free, realloc \- memory allocator"
name (lowercase roman) \- a pithy description of the subject
#
.SH SYNOPSIS
.nf
#
# Put the usage line for a command. 
# For a library, put the calling sequence and argument declarations for 
# each subroutine.  Be sure to specify any necessary include files,
# as well as the actual library name.  
exact command (bold), options (square brackets bold, use | to separate 
alternative options), arguments (square brackets italics)
#
.fi
.SH DESCRIPTION
#
# Here you put the complete description. Use .SS for subsections, .LP
# for paragraphs.
# The names of programs and command options must be in bold. 
# The names of parameters and arguments should be in italics.
#
.SH OPTIONS
#
# Options in bold. Describe options from \fBSYNOPSYS\fR above in fully
# indented paragraphs, preceded by the option.
#
.SH FILES
#
# Describe input and output files (but not down to bits).
#
.SH ENVIRONMENT
#
# Describe any special environment variables
#
.SH PARAMETER FILE
#
# Describe any parameter file
#
.SH EXAMPLE
#
# This section should contain an example that the user can follow
# verbatim.  For a command, this should show a sample command line and output.
# Use the same fonts as in \fBSYNOPSIS\fR. What the user types in should
# be bold, and program response or output should be roman. All commands 
# should be preceded by a representative UNIX prompt.
#
# For a library, you might show an example program (This is usually only 
# done for more complex routines or packages.)
#
.RS .2i
.RE
.SH RETURN VALUES
#
# Describe the return values for each subroutine or command.  The usual
# is to return 0 for normal execution and something else for errors.
#
.SH LIBRARY
#
# Indicate the libraries which need to be linked in (for library routines only)
# in the form of the ldlibs Makefile line, eg "-ldb -lstock -lm"
#
.SH DIAGNOSTICS
#
# Describe error messages and give cautionary advice.
.SH "SEE ALSO"
.nf
#
# List related manual entries and section (lowercase, bold)., eg "file(1)"
# or related documents
.fi
.SH "BUGS AND CAVEATS"
#
# Describe any shortcomings of the programs, known bugs, or surprising 
# results.
.SH AUTHOR
#
# Put the author's name here (person who wrote the code) (roman).
