Package: rpcsvc-proto
Version: 1.4.3-1
Severity: minor
Tags: patch
Dear Maintainer,
here are some notes and editorial fixes for the manual.
The patch is in the attachment.
-.-
Any program (person), that produces man pages, should check its content for
defects by using
groff -mandoc -t -ww -b -z [ -K utf8 | k ] <file>
The same goes for man pages that are used as an input.
For a style guide use
mandoc -T lint
-.-
The difference between the formatted outputs can be seen with:
nroff -man <file1> > <out1>
nroff -man <file2> > <out2>
diff -u <out1> <out2>
and for groff, using
"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -man -Z - "
instead of "nroff -man"
Add the option "-t", if the file contains a table.
Read the output of "diff -u" with "less -R" or similar.
-.-.
If "man" (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-.
Output from "mandoc -T lint rpcgen.1": (possibly shortened list)
mandoc: rpcgen.1:8:14: WARNING: missing date, using "": TH
mandoc: rpcgen.1:41:2: WARNING: skipping paragraph macro: PP after SH
mandoc: rpcgen.1:50:48: STYLE: whitespace at end of input line
mandoc: rpcgen.1:75:68: STYLE: whitespace at end of input line
mandoc: rpcgen.1:81:53: STYLE: whitespace at end of input line
mandoc: rpcgen.1:88:52: STYLE: whitespace at end of input line
mandoc: rpcgen.1:130:59: STYLE: whitespace at end of input line
mandoc: rpcgen.1:131:41: STYLE: whitespace at end of input line
mandoc: rpcgen.1:135:51: STYLE: whitespace at end of input line
mandoc: rpcgen.1:141:5: STYLE: whitespace at end of input line
mandoc: rpcgen.1:250:47: STYLE: whitespace at end of input line
mandoc: rpcgen.1:282:50: STYLE: whitespace at end of input line
mandoc: rpcgen.1:283:42: STYLE: whitespace at end of input line
mandoc: rpcgen.1:303:79: STYLE: whitespace at end of input line
mandoc: rpcgen.1:304:79: STYLE: whitespace at end of input line
mandoc: rpcgen.1:306:83: STYLE: input text line longer than 80 bytes: the
argument but the...
mandoc: rpcgen.1:307:74: STYLE: whitespace at end of input line
mandoc: rpcgen.1:328:43: STYLE: whitespace at end of input line
mandoc: rpcgen.1:355:83: STYLE: input text line longer than 80 bytes: Generate
skeleton co...
mandoc: rpcgen.1:364:12: STYLE: whitespace at end of input line
mandoc: rpcgen.1:384:47: STYLE: whitespace at end of input line
mandoc: rpcgen.1:389:39: STYLE: whitespace at end of input line
mandoc: rpcgen.1:423:22: STYLE: whitespace at end of input line
-.-.
Remove space characters at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
50:is normally used as in the first synopsis where
75:remote procedures on the client side. This code would be created in
81:the remote procedures. This code would be created in
88:it creates servers only for the transport for which
130:A server can use the dispatch table to check authorization
131:and then to execute the service routine;
135:The other three synopses shown above are used when
141:When
250:option can be used in conjunction to produce a
282:This option is useful for doing callback-routines
283:and for users who need to write their own
303:Use the newstyle of rpcgen. This allows procedures to have multiple
arguments.
304:It also uses the style of parameter passing that closely resembles C. So,
when
307:of rpcgen generated code. The newstyle is not the default case because of
328:Compile into server-side stubs for all the
364:The options
384:and their name used inside other structures in
389:Most of these can be avoided by giving
423:server side stubs for
-.-.
Mark a full stop (.) and the exclamation mark (!) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.
When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.
This marking is robust, and independent of the position on the line.
It corresponds to "\ " in TeX, and to "@:" in Texinfo.
2:.\" Copyright (c) 1988,1990 Sun Microsystems, Inc. - All Rights Reserved.
-.-.
Change - to \- if it shall be printed as a minus sign.
rpcgen.1:265:\f4-K\ -1\fP.
rpcgen.1:274:For such servers, \f4rpcgen\fP should be used with \f4-K\ -1\fP.
-.-.
Change a HYPHEN-MINUS (code 0x2D) to a minus(-dash) (\-),
if it
is in front of a name for an option,
is a symbol for standard input,
is a single character used to indicate an option,
or is in the NAME section (man-pages(7)).
N.B. - (0x2D), processed as a UTF-8 file, is changed to a hyphen
(0x2010, groff \[u2010] or \[hy]) in the output.
2:.\" Copyright (c) 1988,1990 Sun Microsystems, Inc. - All Rights Reserved.
265:\f4-K\ -1\fP.
274:For such servers, \f4rpcgen\fP should be used with \f4-K\ -1\fP.
-.-.
Wrong distance between sentences.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
N.B
The number of lines affected can be too large to be in the patch.
75:remote procedures on the client side. This code would be created in
81:the remote procedures. This code would be created in
214:This generates code for the SunOS4.1 style of rpc. It is
218:This generates code for the SysVr4 style of rpc. It is used by the
226:Generate code in ANSI C. This option also generates code that could be
303:Use the newstyle of rpcgen. This allows procedures to have multiple
arguments.
304:It also uses the style of parameter passing that closely resembles C. So,
when
306:the argument but the argument itself. This behaviour is different from the
oldstyle
307:of rpcgen generated code. The newstyle is not the default case because of
355:Generate skeleton code for the remote procedures on the server side. You
would need
-.-.
Test nr. 32:
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
rpcgen.1: line 306 length 83
the argument but the argument itself. This behaviour is different from the
oldstyle
rpcgen.1: line 355 length 83
Generate skeleton code for the remote procedures on the server side. You would
need
-.-.
The name of a man page is typeset in bold and the section in roman
(see man-pages(7)).
161:[see \f4cc\fP(1)],
442:\f4cc\fP(1).
-.-.
Output from "test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z -K utf8":
troff: backtrace: file '<stdin>':3
troff:<stdin>:3: warning: numeric expression missing
troff: backtrace: file '<stdin>':4
troff:<stdin>:4: warning: register 'X' not defined
troff: backtrace: file '<stdin>':50
troff:<stdin>:50: warning: trailing space in the line
troff: backtrace: file '<stdin>':75
troff:<stdin>:75: warning: trailing space in the line
troff: backtrace: file '<stdin>':81
troff:<stdin>:81: warning: trailing space in the line
troff: backtrace: file '<stdin>':88
troff:<stdin>:88: warning: trailing space in the line
troff: backtrace: file '<stdin>':130
troff:<stdin>:130: warning: trailing space in the line
troff: backtrace: file '<stdin>':131
troff:<stdin>:131: warning: trailing space in the line
troff: backtrace: file '<stdin>':135
troff:<stdin>:135: warning: trailing space in the line
troff: backtrace: file '<stdin>':141
troff:<stdin>:141: warning: trailing space in the line
troff: backtrace: file '<stdin>':250
troff:<stdin>:250: warning: trailing space in the line
troff: backtrace: file '<stdin>':282
troff:<stdin>:282: warning: trailing space in the line
troff: backtrace: file '<stdin>':283
troff:<stdin>:283: warning: trailing space in the line
troff: backtrace: file '<stdin>':303
troff:<stdin>:303: warning: trailing space in the line
troff: backtrace: file '<stdin>':304
troff:<stdin>:304: warning: trailing space in the line
troff: backtrace: file '<stdin>':307
troff:<stdin>:307: warning: trailing space in the line
troff: backtrace: file '<stdin>':328
troff:<stdin>:328: warning: trailing space in the line
troff: backtrace: file '<stdin>':364
troff:<stdin>:364: warning: trailing space in the line
troff: backtrace: file '<stdin>':384
troff:<stdin>:384: warning: trailing space in the line
troff: backtrace: file '<stdin>':389
troff:<stdin>:389: warning: trailing space in the line
troff: backtrace: file '<stdin>':423
troff:<stdin>:423: warning: trailing space in the line
-.-
"secs" changed to "seconds" for clarity.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages rpcsvc-proto depends on:
ii libc6 2.38-11
rpcsvc-proto recommends no packages.
rpcsvc-proto suggests no packages.
-- no debconf information
--- rpcgen.1 2024-05-27 22:27:24.147831386 +0000
+++ rpcgen.1.new 2024-05-27 23:46:34.630190827 +0000
@@ -1,117 +1,118 @@
.\" @(#)rpcgen.new.1 1.1 90/11/09 TIRPC 1.0; from 40.10 of 10/10/89
.\" Copyright (c) 1988,1990 Sun Microsystems, Inc. - All Rights Reserved.
-.nr X
+.nr X +0\" Initialize register if not defined on the command line
.if \nX=0 .ds x} rpcgen 1 "" "\&"
.if \nX=1 .ds x} rpcgen 1 ""
.if \nX=2 .ds x} rpcgen 1 "" "\&"
.if \nX=3 .ds x} rpcgen "" "" "\&"
.TH \*(x}
.SH NAME
-\f4rpcgen\f1 \- an RPC protocol compiler
+\f(BIrpcgen\fR \- an RPC protocol compiler
.SH SYNOPSIS
-.ft 4
+.ft BI
.nf
-rpcgen \f2infile\f4
+rpcgen \fIinfile\f(BI
.fi
-.ft 1
+.ft R
.br
-.ft 4
+.ft BI
.nf
-rpcgen [\-D\f2name\f4[=\f2value\f4]] [\-T] [\-K \f2secs\fP] \f2infile\f4
+rpcgen \fR[\fP\-D\fIname\f(BI\fR[\fP=\fIvalue\f(BI\fR]]\fP \fR[\fP\-T\fR]\fP \
+\fR[\fP\-K \fIseconds\fP\fR]\fP \fIinfile\f(BI
.fi
-.ft 1
+.ft R
.br
-.ft 4
+.ft BI
.nf
-rpcgen \-c|\-h|\-l|\-m|\-M|\-t [\-o \f2outfile\f4 ] \f2infile\f4
+rpcgen \-c|\-h|\-l|\-m|\-M|\-t \fR[\fP\-o \fIoutfile\f(BI \fR]\fP
\fIinfile\f(BI
.fi
-.ft 1
+.ft R
.br
-.ft 4
+.ft BI
.nf
-rpcgen [\-I] \-s \f2nettype\f4 [\-o \f2outfile\f4] \f2infile\f4
+rpcgen \fR[\fP\-I\fR]\fP \-s \fInettype\f(BI \fR[\fP\-o \
+\fIoutfile\f(BI\fR]\fP \fIinfile\f(BI
.fi
-.ft 1
+.ft R
.br
-.ft 4
+.ft BI
.nf
-rpcgen \-n \f2netid\f4 [\-o \f2outfile\f4] \f2infile\f4
-.ft 1
+rpcgen \-n \fInetid\f(BI \fR[\fP\-o \fIoutfile\f(BI\fR]\fP \fIinfile\f(BI
+.ft R
.SH DESCRIPTION
-.P
-\f4rpcgen\f1
+\f(BIrpcgen\fR
is a tool that generates C code to implement an RPC protocol.
The input to
-\f4rpcgen\f1
+\f(BIrpcgen\fR
is a language similar to C known as
RPC Language (Remote Procedure Call Language).
.P
-\f4rpcgen\f1
-is normally used as in the first synopsis where
+\f(BIrpcgen\fR
+is normally used as in the first synopsis where
it takes an input file and generates up to four output files.
If the
-\f2infile\f1
+\fIinfile\fR
is named
-\f4proto.x\f1,
+\f(BIproto.x\fR,
then
-\f4rpcgen\f1
+\f(BIrpcgen\fR
will generate a header file in
-\f4proto.h\f1,
+\f(BIproto.h\fR,
XDR routines in
-\f4proto_xdr.c\f1,
+\f(BIproto_xdr.c\fR,
server-side stubs in
-\f4proto_svc.c\f1,
+\f(BIproto_svc.c\fR,
and client-side stubs in
-\f4proto_clnt.c\f1.
+\f(BIproto_clnt.c\fR.
With the
-\f4\-T\f1
+\f(BI\-T\fR
option,
it will also generate the RPC dispatch table in
-\f4proto_tbl.i\f1.
+\f(BIproto_tbl.i\fR.
With the
-\f4\-Sc\f1
+\f(BI\-Sc\fR
option,
-it will also generate sample code which would illustrate how to use the
-remote procedures on the client side. This code would be created in
-\f4proto_client.c\f1.
+it will also generate sample code which would illustrate how to use the
+remote procedures on the client side.
+This code would be created in \f(BIproto_client.c\fR.
With the
-\f4\-Ss\f1
+\f(BI\-Ss\fR
option,
it will also generate a sample server code which would illustrate how to write
-the remote procedures. This code would be created in
-\f4proto_server.c\f1.
+the remote procedures.
+This code would be created in \f(BIproto_server.c\fR.
.P
The server created can be started both by the port monitors
-(for example, \f4inetd\f1 or \f4listen\f1)
+(for example, \f(BIinetd\fR or \f(BIlisten\fR)
or by itself.
When it is started by a port monitor,
-it creates servers only for the transport for which
-the file descriptor \f40\fP was passed.
+it creates servers only for the transport for which
+the file descriptor \f(BI0\fP was passed.
The name of the transport must be specified
by setting up the environmental variable
-\f4PM_TRANSPORT\f1.
+\f(BIPM_TRANSPORT\fR.
When the server generated by
-\f4rpcgen\f1
+\f(BIrpcgen\fR
is executed,
it creates server handles for all the transports
specified in
-\f4NETPATH\f1
+\f(BINETPATH\fR
environment variable,
or if it is unset,
it creates server handles for all the visible transports from
-\f4/etc/netconfig\f1
+\f(BI/etc/netconfig\fR
file.
Note:
the transports are chosen at run time and not at compile time.
.P
-When built for a port monitor (\f4rpcgen\f1 \f4\-I\f1), and that the server
+When built for a port monitor (\f(BIrpcgen\fR \f(BI\-I\fR), and that the server
is self-started, it backgrounds itself by default. A special define symbol
-\f4RPC_SVC_FG\f1 can be used to run the server process in foreground.
+\f(BIRPC_SVC_FG\fR can be used to run the server process in foreground.
.P
The second synopsis provides special features which allow
for the creation of more sophisticated RPC servers.
These features include support for user provided
-\f4#defines\f1
+\f(BI#defines\fR
and RPC dispatch tables.
The entries in the RPC dispatch table contain:
.RS
@@ -127,76 +128,76 @@ a pointer to the input and output argume
the size of these routines
.PD
.RE
-A server can use the dispatch table to check authorization
-and then to execute the service routine;
+A server can use the dispatch table to check authorization
+and then to execute the service routine;
a client library may use it to deal with the details of storage
management and XDR data conversion.
.P
-The other three synopses shown above are used when
+The other three synopses shown above are used when
one does not want to generate all the output files,
but only a particular one.
Some examples of their usage is described in the
EXAMPLE
section below.
-When
-\f4rpcgen\f1
+When
+\f(BIrpcgen\fR
is executed with the
-\f4\-s\f1
+\f(BI\-s\fR
option,
it creates servers for that particular class of transports.
When
executed with the
-\f4\-n\f1
+\f(BI\-n\fR
option,
it creates a server for the transport specified by
-\f2netid\f1.
+\fInetid\fR.
If
-\f2infile\f1
+\fIinfile\fR
is not specified,
-\f4rpcgen\f1
+\f(BIrpcgen\fR
accepts the standard input.
.P
The C preprocessor,
-\f4cc \-E\f1
-[see \f4cc\fP(1)],
+\f(BIcc \-E\fR
+[see \f(BIcc\fP(1)],
is run on the input file before it is actually interpreted by
-\f4rpcgen\f1.
+\f(BIrpcgen\fR.
For each type of output file,
-\f4rpcgen\f1
+\f(BIrpcgen\fR
defines a special preprocessor symbol for use by the
-\f4rpcgen\f1
+\f(BIrpcgen\fR
programmer:
.P
.PD 0
.TP 12
-\f4RPC_HDR\f1
+\f(BIRPC_HDR\fR
defined when compiling into header files
.TP
-\f4RPC_XDR\f1
+\f(BIRPC_XDR\fR
defined when compiling into XDR routines
.TP
-\f4RPC_SVC\f1
+\f(BIRPC_SVC\fR
defined when compiling into server-side stubs
.TP
-\f4RPC_CLNT\f1
+\f(BIRPC_CLNT\fR
defined when compiling into client-side stubs
.TP
-\f4RPC_TBL\f1
+\f(BIRPC_TBL\fR
defined when compiling into RPC dispatch tables
.PD
.P
Any line beginning with
-`\f4%\f1'
+`\f(BI%\fR'
is passed directly into the output file,
uninterpreted by
-\f4rpcgen\f1.
+\f(BIrpcgen\fR.
.P
For every data type referred to in
-\f2infile\f1,
-\f4rpcgen\f1
+\fIinfile\fR,
+\f(BIrpcgen\fR
assumes that there exists a
routine with the string
-\f4xdr_\f1
+\f(BIxdr_\fR
prepended to the name of the data type.
If this routine does not exist in the RPC/XDR
library, it must be provided.
@@ -207,173 +208,177 @@ allows customization of XDR routines.
.P
The following options are available:
.TP
-\f4\-a\f1
+\f(BI\-a\fR
Generate all the files including sample code for client and server side.
.TP
-\f4\-b\f1
-This generates code for the SunOS4.1 style of rpc. It is
-for backward compatibility. This is the default.
+\f(BI\-b\fR
+This generates code for the SunOS4.1 style of rpc.
+It is for backward compatibility.
+This is the default.
.TP
-\f4\-5\f1
-This generates code for the SysVr4 style of rpc. It is used by the
-Transport Independent RPC that is in Svr4 systems.
+\f(BI\-5\fR
+This generates code for the SysVr4 style of rpc.
+It is used by the Transport Independent RPC that is in Svr4 systems.
By default rpcgen generates code for SunOS4.1 stype of rpc.
.TP
-\f4\-c\f1
+\f(BI\-c\fR
Compile into XDR routines.
.TP
-\f4\-C\f1
-Generate code in ANSI C. This option also generates code that could be
-compiled with the C++ compiler. This is the default.
+\f(BI\-C\fR
+Generate code in ANSI C.
+This option also generates code that could be compiled with the C++ compiler.
+This is the default.
.TP
-\f4\-k\f1
+\f(BI\-k\fR
Generate code in K&R C. The default is ANSI C.
.TP
-\f4\-D\f2name\f4[=\f2value\f4]\f1
+\f(BI\-D\fIname\f(BI\fR[\fP=\fIvalue\f(BI\fR]\fP\fR
Define a symbol
-\f2name\f1.
+\fIname\fR.
Equivalent to the
-\f4#define\f1
+\f(BI#define\fR
directive in the source.
If no
-\f2value\f1
+\fIvalue\fR
is given,
-\f2value\f1
-is defined as \f41\f1.
+\fIvalue\fR
+is defined as \f(BI1\fR.
This option may be specified more than once.
.TP
-\f4\-h\f1
+\f(BI\-h\fR
Compile into
-\f4C\f1
+\f(BIC\fR
data-definitions (a header file).
-\f4\-T\f1
-option can be used in conjunction to produce a
+\f(BI\-T\fR
+option can be used in conjunction to produce a
header file which supports RPC dispatch tables.
.TP
-\f4\-I\f1
+\f(BI\-I\fR
Generate a service that can be started from inetd. The default is
-to generate a static service that handles transports selected with \f4\-s\f1.
-Using \f4\-I\f1 allows starting a service by either method.
+to generate a static service that handles transports selected with \f(BI\-s\fR.
+Using \f(BI\-I\fR allows starting a service by either method.
.TP
-\f4-K\f2 secs\f1
-By default, services created using \f4rpcgen\fP wait \f4120\fP seconds
+\f(BI\-K\fI seconds\fR
+By default, services created using \f(BIrpcgen\fP wait \f(BI120\fP seconds
after servicing a request before exiting.
-That interval can be changed using the \f4-K\fP flag.
+That interval can be changed using the \f(BI\-K\fP flag.
To create a server that exits immediately upon servicing a request,
-\f4-K\ 0\fP can be used.
+\f(BI\-K\ 0\fP can be used.
To create a server that never exits, the appropriate argument is
-\f4-K\ -1\fP.
+\f(BI\-K\ \-1\fP.
.IP
When monitoring for a server,
some portmonitors, like
-\f4listen\fP(1M),
+\f(BIlisten\fP(1M),
.I always
spawn a new process in response to a service request.
If it is known that a server will be used with such a monitor, the
server should exit immediately on completion.
-For such servers, \f4rpcgen\fP should be used with \f4-K\ -1\fP.
+For such servers, \f(BIrpcgen\fP should be used with \f(BI\-K\ \-1\fP.
.TP
-\f4\-l\f1
+\f(BI\-l\fR
Compile into client-side stubs.
.TP
-\f4\-m\f1
+\f(BI\-m\fR
Compile into server-side stubs,
but do not generate a \(lqmain\(rq routine.
-This option is useful for doing callback-routines
-and for users who need to write their own
+This option is useful for doing callback-routines
+and for users who need to write their own
\(lqmain\(rq routine to do initialization.
.TP
-\f4\-M\f1
+\f(BI\-M\fR
Generate multithread-safe stubs for passing arguments
and results between rpcgen-generated code and user written code.
This option is useful for users who want to use threads in their code.
.TP
-\f4\-n \f2netid\f1
+\f(BI\-n \fInetid\fR
Compile into server-side stubs for the transport
specified by
-\f2netid\f1.
+\fInetid\fR.
There should be an entry for
-\f2netid\f1
+\fInetid\fR
in the
netconfig database.
This option may be specified more than once,
so as to compile a server that serves multiple transports.
.TP
-\f4\-N\f1
-Use the newstyle of rpcgen. This allows procedures to have multiple arguments.
-It also uses the style of parameter passing that closely resembles C. So, when
+\f(BI\-N\fR
+Use the newstyle of rpcgen.
+This allows procedures to have multiple arguments.
+It also uses the style of parameter passing that closely resembles C.
+So, when
passing an argument to a remote procedure you do not have to pass a pointer to
-the argument but the argument itself. This behaviour is different from the
oldstyle
-of rpcgen generated code. The newstyle is not the default case because of
-backward compatibility.
+the argument but the argument itself.
+This behaviour is different from the oldstyle of rpcgen generated code.
+The newstyle is not the default case because of backward compatibility.
.TP
-\f4\-o \f2outfile\f1
+\f(BI\-o \fIoutfile\fR
Specify the name of the output file.
If none is specified,
standard output is used
-(\f4\-c\f1,
-\f4\-h\f1,
-\f4\-l\f1,
-\f4\-m\f1,
-\f4\-n\f1,
-\f4\-s\f1,
-\f4\-Sc\f1,
-\f4\-Sm\f1,
-\f4\-Ss\f1,
+(\f(BI\-c\fR,
+\f(BI\-h\fR,
+\f(BI\-l\fR,
+\f(BI\-m\fR,
+\f(BI\-n\fR,
+\f(BI\-s\fR,
+\f(BI\-Sc\fR,
+\f(BI\-Sm\fR,
+\f(BI\-Ss\fR,
and
-\f4\-t\f1
+\f(BI\-t\fR
modes only).
.TP
-\f4\-s \f2nettype\f1
-Compile into server-side stubs for all the
+\f(BI\-s \fInettype\fR
+Compile into server-side stubs for all the
transports belonging to the class
-\f2nettype\f1.
+\fInettype\fR.
The supported classes are
-\f4netpath\f1,
-\f4visible\f1,
-\f4circuit_n\f1,
-\f4circuit_v\f1,
-\f4datagram_n\f1,
-\f4datagram_v\f1,
-\f4tcp\f1,
+\f(BInetpath\fR,
+\f(BIvisible\fR,
+\f(BIcircuit_n\fR,
+\f(BIcircuit_v\fR,
+\f(BIdatagram_n\fR,
+\f(BIdatagram_v\fR,
+\f(BItcp\fR,
and
-\f4udp\f1
-[see \f4rpc\fP(3N)
+\f(BIudp\fR
+[see \f(BIrpc\fP(3N)
for the meanings associated with these classes].
This option may be specified more than once.
Note:
the transports are chosen at run time and not at compile time.
.TP
-\f4\-Sc\f1
+\f(BI\-Sc\fR
Generate sample code to show the use of remote procedure and how to bind
to the server before calling the client side stubs generated by rpcgen.
.TP
-\f4\-Sm\f1
+\f(BI\-Sm\fR
Generate a sample Makefile which can be used for compiling the application.
.TP
-\f4\-Ss\f1
-Generate skeleton code for the remote procedures on the server side. You would
need
-to fill in the actual code for the remote procedures.
+\f(BI\-Ss\fR
+Generate skeleton code for the remote procedures on the server side.
+You would need to fill in the actual code for the remote procedures.
.TP
-\f4\-t\f1
+\f(BI\-t\fR
Compile into RPC dispatch table.
.TP
-\f4\-T\f1
+\f(BI\-T\fR
Generate the code to support RPC dispatch tables.
.P
-The options
-\f4\-c\f1,
-\f4\-h\f1,
-\f4\-l\f1,
-\f4\-m\f1,
-\f4\-s\f1
+The options
+\f(BI\-c\fR,
+\f(BI\-h\fR,
+\f(BI\-l\fR,
+\f(BI\-m\fR,
+\f(BI\-s\fR
and
-\f4\-t\f1
+\f(BI\-t\fR
are used exclusively to generate a particular type of file,
while the options
-\f4\-D\f1
+\f(BI\-D\fR
and
-\f4\-T\f1
+\f(BI\-T\fR
are global and can be used with the other options.
.br
.ne 5
@@ -381,62 +386,62 @@ are global and can be used with the othe
The RPC Language does not support nesting of structures.
As a work-around,
structures can be declared at the top-level,
-and their name used inside other structures in
+and their name used inside other structures in
order to achieve the same effect.
.P
Name clashes can occur when using program definitions,
since the apparent scoping does not really apply.
-Most of these can be avoided by giving
+Most of these can be avoided by giving
unique names for programs,
versions,
procedures and types.
.P
The server code generated with
-\f4\-n\f1
+\f(BI\-n\fR
option refers to the transport indicated by
-\f2netid\f1
+\fInetid\fR
and hence is very site specific.
.SH EXAMPLE
The following example:
.IP
-.ft 4
+.ft BI
$ rpcgen \-T prot.x
-.ft 1
+.ft R
.P
generates the five files:
-\f4prot.h\f1,
-\f4prot_clnt.c\f1,
-\f4prot_svc.c\f1,
-\f4prot_xdr.c\f1
+\f(BIprot.h\fR,
+\f(BIprot_clnt.c\fR,
+\f(BIprot_svc.c\fR,
+\f(BIprot_xdr.c\fR
and
-\f4prot_tbl.i\f1.
+\f(BIprot_tbl.i\fR.
.P
The following example sends the C data-definitions (header file)
to the standard output.
.IP
-.ft 4
+.ft BI
$ rpcgen \-h prot.x
-.ft 1
+.ft R
.P
To send the test version of the
-\f4-DTEST\f1,
-server side stubs for
+\f(BI\-DTEST\fR,
+server side stubs for
all the transport belonging to the class
-\f4datagram_n\f1
+\f(BIdatagram_n\fR
to standard output, use:
.IP
-.ft 4
+.ft BI
$ rpcgen \-s datagram_n \-DTEST prot.x
-.ft 1
+.ft R
.P
To create the server side stubs for the transport indicated
by
-\f2netid\f1
-\f4tcp\f1,
+\fInetid\fR
+\f(BItcp\fR,
use:
.IP
-.ft 4
+.ft BI
$ rpcgen \-n tcp \-o prot_svc.c prot.x
-.ft 1
+.ft R
.SH "SEE ALSO"
-\f4cc\fP(1).
+\f(BIcc\fP(1).
