rpms/man-pages
7
0
Fork 0
Code Issues Pull Requests Releases Activity

- update to 3.00

Browse Source 
- source files changes
This commit is contained in:
Ivana Varekova 2008-06-18 10:26:46 +00:00
parent ae24a9934e
commit e7ba749ed5
10 changed files with 28 additions and 949 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
.cvsignore
View File

@ -1,5 +1,6 @@
man-pages-extralocale.tar.bz2
man2.tar.gz
man2_sys2.1.tar.gz
man-suid-bins.tar.bz2
man-pages-2.80.tar.bz2
man-pages-3.00.tar.bz2
man-pages-posix-2003-a.tar.bz2
man-pages_syscalls.tar.bz2
man-pages_add-01.tar.bz2

92
gai.conf.5
View File

@ -1,92 +0,0 @@
.\" A man page for gai.conf. -*- nroff -*-
.\"
.\" Copyright (C) 2006 Red Hat, Inc. All rights reserved.
.\"
.\" This copyrighted material is made available to anyone wishing to use,
.\" modify, copy, or redistribute it subject to the terms and conditions of the
.\" GNU General Public License v.2.
.\"
.\" This program is distributed in the hope that it will be useful, but WITHOUT
.\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
.\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
.\" more details.
.\"
.\" You should have received a copy of the GNU General Public License along
.\" with this program; if not, write to the Free Software Foundation, Inc.,
.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\"
.\" Author: Ulrich Drepper <drepper@redhat.com>
.TH gai.conf 5 "May 2006" gai.conf
.SH NAME
gai.conf \- getaddrinfo(3) configuration file
.SH DESCRIPTION
A call to
.BR getaddrinfo (3)
might return multiple answers. According to RFC 3484 these answers must
be sorted so that the answer with the highest success rate is first in
the list. The RFC provides and algorithm for the sorting. The static
rules are not always adequate, though. For this reason the RFC also
requires that system administrators get the chance to dynamically change
the sorting. For the glibc implementation this can be achieved with
the
.BR /etc/gai.conf
file.
.PP
Each line in the configuration file consists of a keyword and its
parameters. White spaces in any place are ignored. Lines starting
with `#' are comments and are ignored.
.PP
The keywords currently recognized are:
.TP
\fBlabel\fR \fInetmask\fR \fIprecedence\fR
The value is added to the label table used in the RFC 3484 sorting.
If any \fBlabel\fR definition is present in the configuration file
is present the default table is not used. All the label definitions
of the default table which are to be maintained have to be duplicated.
Following the keyword the line has to contain a network mask and a label
value.
.TP
\fBprecedence\fR \fInetmask\fR \fIprecedence\fR
This keyword is similar to \fBlabel\fR but instead the value is added
to the precendence table as specified in RFC 3484. Once again, the
presence of a single \fBprecedence\fR line in the configuration file
causes the default table to not be used.
.TP
\fBreload\fR <\fByes\fR|\fBno\fR>
This keyword control whether a process checks whether the configuration
file has been changes since the last time it was read. If the value is
`\fByes\fR' the file is re-read. This might cause problems in multi-threaded
applications and is generally a bad idea. The default is `\fBno\fR'.
.SH EXAMPLE
The default table according to RFC 3484 would be specified with the
following configuration file:
.nf
label ::1/128 0
label ::/0 1
label 2002::/16 2
label ::/96 3
label ::ffff:0:0/96 4
precendence ::1/128 50
precendence ::/0 40
precendence 2002::/16 30
precendence ::/96 20
precendence ::ffff:0:0/96 10
.SH FILES
\fI/etc/gai.conf\fR
.SH AUTHOR
Ulrich Drepper <drepper@redhat.com>
.SH SEE ALSO
.BR getaddrinfo(3),
RFC 3484

44
man-pages.spec
View File

@ -1,24 +1,23 @@
%define posix_version 2003
%define posix_release a
Summary: Man (manual) pages from the Linux Documentation Project
Name: man-pages
Version: 2.80
Release: 2%{?dist}
Version: 3.00
Release: 1%{?dist}
License: GPLv2+, GLP, BSD, MIT, Copyright only, IEEE
Group: Documentation
URL: http://www.kernel.org/pub/linux/docs/manpages/
Source0: http://www.kernel.org/pub/linux/docs/manpages/man-pages-%{version}.tar.bz2
Source1: rpcgen.1
Source2: resolver.5
# from Debian:
Source3: uuname.1
Source6: man-pages-extralocale.tar.bz2
Source9: man2.tar.gz
Source10: sln.8
Source11: man2_sys.tar.gz
Source12: gai.conf.5
Source13: nss.5
Source14: man2_sys2.1.tar.gz
# POSIX man pages
Source1: http://www.kernel.org/pub/linux/docs/man-pages/man-pages-posix/man-pages-posix-%{posix_version}-%{posix_release}.tar.bz2
Source2: man-pages_add-01.tar.bz2
Source3: man-pages-extralocale.tar.bz2
Source4: man-pages_syscalls.tar.bz2
# IBM-supplied man pages for suid binaries:
Source15: man-suid-bins.tar.bz2
Source5: man-suid-bins.tar.bz2
Patch1: man-pages-1.51-iconv.patch
Patch28: man-pages-2.46-nscd.patch
Patch36: man-pages-2.63-unimplemented.patch
@ -44,17 +43,10 @@ A large collection of man pages (documentation) from the Linux
Documentation Project (LDP).
%prep
%setup -q -a 6 -a 9 -a 11 -a 14 -a 15
%setup -q -n %{name}-%{version} -a 1 -a 2 -a 3 -a 4 -a 5
for manpage in \
%{SOURCE1} \
%{SOURCE2} \
%{SOURCE10} \
%{SOURCE12} \
%{SOURCE13}
do
cp -p $manpage man${manpage##*.}
done
mv man-pages-posix-%{posix_version}-%{posix_release}/* ./
rmdir man-pages-posix-%{posix_version}-%{posix_release}
%patch1 -p1
%patch28 -p1
@ -181,6 +173,10 @@ rm -rf $RPM_BUILD_ROOT
%lang(en) %{_mandir}/en/man*
%changelog
* Wed Jun 18 2008 Ivana Varekova <varekova@redhat.com> - 3.00-1
- update to 3.00
- source files changes
* Wed Jun 11 2008 Ivana Varekova <varekova@redhat.com> - 2.80-2
- reformulate the malloc_hook patch

BIN
man2_sys.tar.gz
View File

Binary file not shown.

109
nss.5
View File

@ -1,109 +0,0 @@
.\" A man page for /etc/default/nss. -*- nroff -*-
.\"
.\" Copyright (C) 2006 Red Hat, Inc. All rights reserved.
.\"
.\" This copyrighted material is made available to anyone wishing to use,
.\" modify, copy, or redistribute it subject to the terms and conditions of the
.\" GNU General Public License v.2.
.\"
.\" This program is distributed in the hope that it will be useful, but WITHOUT
.\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
.\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
.\" more details.
.\"
.\" You should have received a copy of the GNU General Public License along
.\" with this program; if not, write to the Free Software Foundation, Inc.,
.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\"
.\" Author: Ulrich Drepper <drepper@redhat.com>
.TH nss 5 "May 2006" nss
.SH NAME
nss \- Name Service Switch configuration file
.SH DESCRIPTION
Each call to a function which retrieves data from a system database
like the password or group database is handled by the Name Service
Switch implementation in the GNU C library. The various services
provided are implemented by independent modules, each of which
naturally varies widely from the other.
.PP
The default implementations coming with the GNU C library are by
default conservative and do not use unsafe data. This might be
very costly in some situations, especially when the databases
are large. Some modules allow the system administrator to request
taking shortcuts if these are known to be safe. It is then the
system administrator's responsibility to ensure the assumption
is correct.
.PP
There are other modules where the implementation changed over time.
If an implementation used to sacrifize speed for memory consumption
it might create problems if the preference is switched.
.PP
The \fI/etc/default/nss\fR file contains a number of variable
assignments. Each variable controls the behavior of one or more
NSS modules. White spaces are ignored. Lines beginning with `#'
are treated as comments.
.PP
The variables currently recognized are:
.TP
\fBNETID_AUTHORITATIVE =\fR \fITRUE\fR|\fIFALSE\fR
If set to TRUE, the NIS backend for the
.BR initgroups (3)
function will accept the information
from the netid.byname NIS map as authoritative. This can speed up the
function significantly if the group.byname map is large. The content
of the netid.byname map is used \fBas is\fR. The system administrator has
to make sure it is correctly generated.
.TP
\fBSERVICES_AUTHORITATIVE =\fR \fITRUE\fR|\fIFALSE\fR
If set to TRUE, the NIS backend for the
.BR getservbyname (3)
and
.BR getservbyname_r (3)
function will assume
services.byservicename NIS map exists and is authoritative, particularly
that it contains both keys with /proto and without /proto for both
primary service names and service aliases. The system administrator
has to make sure it is correctly generated.
.TP
\fBSETENT_BATCH_READ =\fR \fITRUE\fR|\fIFALSE\fR
If set to TRUE, the NIS backend for the
.BR setpwent (3)
and
.BR setgrent (3)
functions will read the entire
database at once and then hand out the requests one by one from
memory with every corresponding
.BR getpwent (3)
or
.BR getgrent (3)
call respectively. Otherwise each
.BR getpwent (3)
or
.BR getgrent (3)
call might result into a network communication with the server to get
the next entry.
.SH EXAMPLE
The default configuration corresponds to the
following configuration file:
.nf
NETID_AUTHORITATIVE=FALSE
SERVICES_AUTHORITATIVE=FALSE
SETENT_BATCH_READ=FALSE
.SH FILES
\fI/etc/default/nss\fR
.SH AUTHOR
Ulrich Drepper <drepper@redhat.com>
.SH SEE ALSO
\fInsswitch.conf\fR

228
resolver.5
View File

@ -1,228 +0,0 @@
.\" Copyright (c) 1986 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms are permitted
.\" provided that the above copyright notice and this paragraph are
.\" duplicated in all such forms and that any documentation,
.\" advertising materials, and other materials related to such
.\" distribution and use acknowledge that the software was developed
.\" by the University of California, Berkeley. The name of the
.\" University may not be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
.\"
.\" @(#)resolver.5 5.9 (Berkeley) 12/14/89
.\" $Id: resolver.5,v 8.6 1999/05/21 00:01:02 vixie Exp $
.\"
.\" Revised by Mike MacCana
.\"
.Dd June 23, 2004
.Dt RESOLVER 5
.Os BSD 4
.Sh NAME
.Nm resolver
.Nd DNS client
.Sh SYNOPSIS
.Pa /etc/resolv.conf
.Sh DESCRIPTION
The
.Nm resolver
is the DNS client used on most Linux and BSD systems. It comes with glibc.
Its configuration file
.Pa /etc/resolv.conf
(note the spelling) determines the DNS servers to use, and various other options - see below.
.Pp
Almost all machines have a DNS server set up in this file - if it
doesn't exist, the system will assume there's a DNS server running on the local
machine, and work out the search path from the machines domain name.
.Pp
The config file is read the first time the DNS client is invoked by a process.
.Pp
The different configuration options are:
.Bl -tag -width "nameserver"
.It Li nameserver
IP address of a DNS server to use. Multiple name servers may be listed, each on their own line. The
.Nm resolver
will use them in order listed - if the first server times out answering the query, the next server will be tried, and so on. If the
.Li resolver
runs out out of name servers, the first server will be queried again, until a maximum number of retries are made.
.Pp
The maximum number of DNS servers to use is set by
.Dv MAXNS
(see
.Pa <resolv.h>
)
.It Li search
Domain(s) to use for DNS lookups when no domain is specified. List each domain
following the
.Li search
keyword with spaces or tabs between them. Each possible domain will be checked in order until a match is found. Note that this process may be slow (queries will time out if no server is available for a domain) and will generate a lot of network traffic if the servers for the listed domains aren't local.
.Pp
The search list is currently limited to six domains with a total of 256 characters.
If
.Li search
isn't specified, the search list will be determined from the local domain name (whatever comes after the first dot). If the host name doesn't contain a domain, the root domain is used.
.Pp
By default, it
.Li search
contains only the local domain name.
.It Li domain
Local domain name. You can use this instead of the
.Li search
option to specify a single domain to check if a hostname isn't specified. Most people just use
.Li search
instead (that option lets you use multiple servers,
.Li domain
doesn't). You can't use
.Li domain
and
.Li search
at the same time - they're mutually exclusive.
.Pp
If
.Li domain
isn't specified, the domain will be determined from the local domain name (whatever comes after the first dot). If the host name doesn't contain a domain, the root domain is used.
.It Li sortlist
Sorts addresses returned by the
.Li gethostbyname
system call.
A
.Li sortlist
is specified by IP address netmask pairs. The netmask is
optional and defaults to the natural netmask of the net. The IP address
and optional network pairs are separated by slashes. Up to 10 pairs may
be specified. For example:
.Bd -literal -offset indent
sortlist 130.155.160.0/255.255.240.0 130.155.0.0
.Ed
.It Li options
Allows certain internal
.Nm resolver
variables to be modified.
The syntax is
.D1 Li options Ar option ...
where
.Ar option
is one of the following:
.Bl -tag -width "ndots:n "
.It Li debug
sets
.Dv RES_DEBUG
in
.Ft _res.options .
.It Li ndots: Ns Ar n
sets a threshold for the number of dots which
must appear in a name given to
.Fn res_query
(see
.Xr resolver 3 )
before an
.Em initial absolute query
will be made. The default for
.Ar n
is
.Dq 1 ,
meaning that if there are
.Em any
dots in a name, the name will be tried first as an absolute name before any
.Em search list
elements are appended to it.
.It Li timeout: Ns Ar n
sets the amount of time the resolver will wait for a response from a remote
name server before retrying the query via a different name server. Measured in
seconds, the default is
.Dv RES_TIMEOUT
(see
.Pa <resolv.h> ).
.It Li attempts: Ns Ar n
sets the number of times the resolver will send a query to its name servers
before giving up and returning an error to the calling application. The
default is
.Dv RES_DFLRETRY
(see
.Pa <resolv.h> ).
.It Li rotate
sets
.Dv RES_ROTATE
in
.Ft _res.options ,
which causes round robin selection of nameservers from among those listed.
This has the effect of spreading the query load among all listed servers,
rather than having all clients try the first listed server first every time.
.It Li no-check-names
sets
.Dv RES_NOCHECKNAME
in
.Ft _res.options ,
which disables the modern BIND checking of incoming host names and mail names
for invalid characters such as underscore (_), non-ASCII, or control characters.
.It Li inet6
sets
.Dv RES_USE_INET6
in
.Ft _res.options .
This has the effect of trying a AAAA query before an A query inside the
.Ft gethostbyname
function, and of mapping IPv4 responses in IPv6 ``tunnelled form'' if no
AAAA records are found but an A record set exists.
.It Li ip6-dotint / no-ip6-dotint
sets / clears the
.Dv RES_NOIP6DOTINT
bit in
.Ft _res.options ,
which when set (ip6-dotint) will enable reverse IPv6 lookups to be made in the (deprecated)
ip6.int zone; when clear (no-ip6-dotint), reverse IPv6 lookups are made in the ip6.arpa zone
by default.
.It Li ip6-bytestring
sets
.Dv RES_USEBSTRING
in
.Ft _res.options .
This causes reverse IPv6 lookups to be made using the bit-label
format of RFC 2673; if not set, then nibble format is used.
.El
.El
.Pp
The
.Li domain
and
.Li search
keywords are mutually exclusive.
If more than one instance of these keywords is present,
the last instance wins.
.Pp
The
.Li search
keyword of a system's
.Pa resolv.conf
file can be
overridden on a per-process basis by setting the environment variable
.Dq Ev LOCALDOMAIN
to a space-separated list of search domains.
.Pp
The
.Li options
keyword of a system's
.Pa resolv.conf
file can be amended on a per-process basis by setting the environment variable
.Dq Ev RES_OPTIONS to a space-separated list of
.Nm resolver
options as explained above under
.Li options .
.Pp
The keyword and value must appear on a single line, and the keyword
(e.g.,
.Li nameserver )
must start the line. The value follows the keyword, separated by white space.
.Sh FILES
.Pa /etc/resolv.conf
.Pa <resolv.h>
.Sh SEE ALSO
.Xr gethostbyname 3 ,
.Xr hostname 7 ,
.Xr named 8 ,
.Xr resolver 3 ,
.Xr resolver 5 .
.Dq Name Server Operations Guide for Sy BIND

434
rpcgen.1
View File

@ -1,434 +0,0 @@
.\" @(#)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
.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
.SH SYNOPSIS
.ft 4
.nf
rpcgen \f2infile\f4
.fi
.ft 1
.br
.ft 4
.nf
rpcgen [\-D\f2name\f4[=\f2value\f4]] [\-T] [\-K \f2secs\fP] \f2infile\f4
.fi
.ft 1
.br
.ft 4
.nf
rpcgen \-c|\-h|\-l|\-m|\-t [\-o \f2outfile\f4 ] \f2infile\f4
.fi
.ft 1
.br
.ft 4
.nf
rpcgen [\-I] \-s \f2nettype\f4 [\-o \f2outfile\f4] \f2infile\f4
.fi
.ft 1
.br
.ft 4
.nf
rpcgen \-n \f2netid\f4 [\-o \f2outfile\f4] \f2infile\f4
.ft 1
.SH DESCRIPTION
.P
\f4rpcgen\f1
is a tool that generates C code to implement an RPC protocol.
The input to
\f4rpcgen\f1
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
it takes an input file and generates up to four output files.
If the
\f2infile\f1
is named
\f4proto.x\f1,
then
\f4rpcgen\f1
will generate a header file in
\f4proto.h\f1,
XDR routines in
\f4proto_xdr.c\f1,
server-side stubs in
\f4proto_svc.c\f1,
and client-side stubs in
\f4proto_clnt.c\f1.
With the
\f4\-T\f1
option,
it will also generate the RPC dispatch table in
\f4proto_tbl.i\f1.
With the
\f4\-Sc\f1
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.
With the
\f4\-Ss\f1
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.
.P
The server created can be started both by the port monitors
(for example, \f4inetd\f1 or \f4listen\f1)
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.
The name of the transport must be specified
by setting up the environmental variable
\f4PM_TRANSPORT\f1.
When the server generated by
\f4rpcgen\f1
is executed,
it creates server handles for all the transports
specified in
\f4NETPATH\f1
environment variable,
or if it is unset,
it creates server handles for all the visible transports from
\f4/etc/netconfig\f1
file.
Note:
the transports are chosen at run time and not at compile time.
When 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.
.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
and RPC dispatch tables.
The entries in the RPC dispatch table contain:
.RS
.PD 0
.TP 3
\(bu
pointers to the service routine corresponding to that procedure,
.TP
\(bu
a pointer to the input and output arguments
.TP
\(bu
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 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
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
is executed with the
\f4\-s\f1
option,
it creates servers for that particular class of transports.
When
executed with the
\f4\-n\f1
option,
it creates a server for the transport specified by
\f2netid\f1.
If
\f2infile\f1
is not specified,
\f4rpcgen\f1
accepts the standard input.
.P
The C preprocessor,
\f4cc \-E\f1
[see \f4cc\fP(1)],
is run on the input file before it is actually interpreted by
\f4rpcgen\f1.
For each type of output file,
\f4rpcgen\f1
defines a special preprocessor symbol for use by the
\f4rpcgen\f1
programmer:
.P
.PD 0
.TP 12
\f4RPC_HDR\f1
defined when compiling into header files
.TP
\f4RPC_XDR\f1
defined when compiling into XDR routines
.TP
\f4RPC_SVC\f1
defined when compiling into server-side stubs
.TP
\f4RPC_CLNT\f1
defined when compiling into client-side stubs
.TP
\f4RPC_TBL\f1
defined when compiling into RPC dispatch tables
.PD
.P
Any line beginning with
`\f4%\f1'
is passed directly into the output file,
uninterpreted by
\f4rpcgen\f1.
.P
For every data type referred to in
\f2infile\f1,
\f4rpcgen\f1
assumes that there exists a
routine with the string
\f4xdr_\f1
prepended to the name of the data type.
If this routine does not exist in the RPC/XDR
library, it must be provided.
Providing an undefined data type
allows customization of XDR routines.
.br
.ne 10
.P
The following options are available:
.TP
\f4\-a\f1
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 compatibilty. 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.
By default rpcgen generates code for SunOS4.1 stype of rpc.
.TP
\f4\-c\f1
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.
.TP
\f4\-k\f1
Generate code in K&R C. The default is ANSI C.
.TP
\f4\-D\f2name\f4[=\f2value\f4]\f1
Define a symbol
\f2name\f1.
Equivalent to the
\f4#define\f1
directive in the source.
If no
\f2value\f1
is given,
\f2value\f1
is defined as \f41\f1.
This option may be specified more than once.
.TP
\f4\-h\f1
Compile into
\f4C\f1
data-definitions (a header file).
\f4\-T\f1
option can be used in conjunction to produce a
header file which supports RPC dispatch tables.
.TP
\f4\-I\f1
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.
.TP
\f4-K\f2 secs\f1
By default, services created using \f4rpcgen\fP wait \f4120\fP seconds
after servicing a request before exiting.
That interval can be changed using the \f4-K\fP flag.
To create a server that exits immediately upon servicing a request,
\f4-K\ 0\fP can be used.
To create a server that never exits, the appropriate argument is
\f4-K\ -1\fP.
.IP
When monitoring for a server,
some portmonitors, like
\f4listen\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.
.TP
\f4\-l\f1
Compile into client-side stubs.
.TP
\f4\-m\f1
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
\(lqmain\(rq routine to do initialization.
.TP
\f4\-n \f2netid\f1
Compile into server-side stubs for the transport
specified by
\f2netid\f1.
There should be an entry for
\f2netid\f1
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
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.
.TP
\f4\-o \f2outfile\f1
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\-s\Sc,
\f4\-s\Ss
and
\f4\-t\f1
modes only).
.TP
\f4\-s \f2nettype\f1
Compile into server-side stubs for all the
transports belonging to the class
\f2nettype\f1.
The supported classes are
\f4netpath\f1,
\f4visible\f1,
\f4circuit_n\f1,
\f4circuit_v\f1,
\f4datagram_n\f1,
\f4datagram_v\f1,
\f4tcp\f1,
and
\f4udp\f1
[see \f4rpc\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
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\-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.
.TP
\f4\-t\f1
Compile into RPC dispatch table.
.TP
\f4\-T\f1
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
and
\f4\-t\f1
are used exclusively to generate a particular type of file,
while the options
\f4\-D\f1
and
\f4\-T\f1
are global and can be used with the other options.
.br
.ne 5
.SH NOTES
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
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
unique names for programs,
versions,
procedures and types.
.P
The server code generated with
\f4\-n\f1
option refers to the transport indicated by
\f2netid\f1
and hence is very site specific.
.SH EXAMPLE
The following example:
.IP
.ft 4
$ rpcgen \-T prot.x
.ft 1
.P
generates the five files:
\f4prot.h\f1,
\f4prot_clnt.c\f1,
\f4prot_svc.c\f1,
\f4prot_xdr.c\f1
and
\f4prot_tbl.i\f1.
.P
The following example sends the C data-definitions (header file)
to the standard output.
.IP
.ft 4
$ rpcgen \-h prot.x
.ft 1
.P
To send the test version of the
\f4-DTEST\f1,
server side stubs for
all the transport belonging to the class
\f4datagram_n\f1
to standard output, use:
.IP
.ft 4
$ rpcgen \-s datagram_n \-DTEST prot.x
.ft 1
.P
To create the server side stubs for the transport indicated
by
\f2netid\f1
\f4tcp\f1,
use:
.IP
.ft 4
$ rpcgen \-n tcp \-o prot_svc.c prot.x
.ft 1
.SH "SEE ALSO"
\f4gcc\fP(1).

23
sln.8
View File

@ -1,23 +0,0 @@
.\" Nicolai Langfeldt (janl@math.uio.no)
.\" In the public domain.
.TH SLN 8 "20 June 1997" "Linux 2.0" "Linux Programmer's Manual"
.SH NAME
sln \- static ln
.SH SYNOPSIS
.BI sln " source dest"
.SH DESCRIPTION
.B sln
symbolically links
.I dest
to
.IR source .
It is statically linked, needing no dynamic linking at all. Thus
.B sln
is useful to make symbolic links to dynamic libraries if the
dynamic linking system for some reason is nonfunctional.
.SH "SEE ALSO"
.BR ln(1)
.BR ldconfig(8)
.BR ld.so(8)
.\" .SH AUTHOR
.\" Mike Parker and David MacKenzie.

7
sources
View File

@ -1,5 +1,6 @@
57f2e0500d177e05647990eae439a8ee man-pages-extralocale.tar.bz2
af09d031dcee66929510e078d00066f2 man2.tar.gz
fbc03fdbc665e24961d30dad3ed8596d man2_sys2.1.tar.gz
a9c6a14e5b34c18c3684a0b68322572f man-suid-bins.tar.bz2
a8ab937d11e3c070c7958411125519b3 man-pages-2.80.tar.bz2
e33a7c2e5ae9e5d3b3ed71568a740e30 man-pages-3.00.tar.bz2
7c78aff03c0a6767ba483d34f19e4b09 man-pages-posix-2003-a.tar.bz2
bf0d94a7faf6dc0db31325dbf576fd84 man-pages_syscalls.tar.bz2
4ae755c6caaa035cb7737bf4a3ec7927 man-pages_add-01.tar.bz2

33
uuname.1
View File

@ -1,33 +0,0 @@
.\" This is under the same license as uuname itself
.TH UUNAME 1
.SH NAME
uuname \- List the names of the known remote UUCP sites.
.SH SYNOPSIS
.B uuname
[\fI\-a\fR] [\fI\-l\fR] [\fI\-I file\fR]
.SH DESCRIPTION
.I Uuname
is a program that lists the names of the known remote UUCP sites.
.SH OPTIONS
.TP
\fB-a\fR, \fB--aliases\fR
Display aliases.
.TP
\fB-l\fR, \fB--local\fR
Print the local name.
.TP
\fB-I\fR, \fB--config\fR \fIfile\fR
Set the configuration file to use.
.TP
\fB-v\fR, \fB--version\fR
Print the software version and exit.
.TP
\fB--help\fR
Print a help screen and exit.
.SH BUGS
None apparent.
.SH "SEE ALSO"
.BR uucp(1)
.SH AUTHOR
This manual page is a quick write-up for Debian done by Kevin Kreamer
<kkreamer@etherhogz.org>, by making a manpage out of \fBuuname\fR \fI--help\fR.