1*39d81999Snjoly.\" $NetBSD: rpc.5,v 1.11 2013/03/15 19:32:31 njoly Exp $ 2fbe0b56aSfvdl.\" @(#)rpc.4 1.17 93/08/30 SMI; from SVr4 3fbe0b56aSfvdl.\" Copyright 1989 AT&T 4fbe0b56aSfvdl.Dd December 10, 1991 53fc63f6bScgd.Dt RPC 5 6f623bd13Sjoerg.Os 73fc63f6bScgd.Sh NAME 83fc63f6bScgd.Nm rpc 93fc63f6bScgd.Nd rpc program number data base 10fbe0b56aSfvdl.Sh SYNOPSIS 11*39d81999Snjoly.Pa /etc/rpc 123fc63f6bScgd.Sh DESCRIPTION 133fc63f6bScgdThe 14fbe0b56aSfvdl.Nm 15fbe0b56aSfvdlfile is a local source containing user readable names that 16fbe0b56aSfvdlcan be used in place of RPC program numbers. 173fc63f6bScgd.Pp 1867809b1cSwizThe 1967809b1cSwiz.Nm 2067809b1cSwizfile has one line for each RPC program name. 2167809b1cSwizThe line has the following format: 22fbe0b56aSfvdl.Pp 23f623bd13Sjoerg.Dl name-of-the-RPC-program RPC-program-number aliases 243fc63f6bScgd.Pp 253fc63f6bScgdItems are separated by any number of blanks and/or 263fc63f6bScgdtab characters. 2771e62d7dSlukemA hash 2871e62d7dSlukem.Pq Dq \&# 2971e62d7dSlukemindicates the beginning of a comment; 30fbe0b56aSfvdlcharacters up to the end of the line are not interpreted 31fbe0b56aSfvdlby routines which search the file. 3242704c41Swiz.Sh FILES 33*39d81999Snjoly.Pa /etc/rpc 343fc63f6bScgd.Sh EXAMPLES 35fbe0b56aSfvdlBelow is an example of an RPC data base: 36fbe0b56aSfvdl.Pp 37fbe0b56aSfvdl.Bd -literal 383fc63f6bScgd# 39fbe0b56aSfvdl# rpc 403fc63f6bScgd# 41fbe0b56aSfvdlrpcbind 100000 portmap sunrpc portmapper 423fc63f6bScgdrusersd 100002 rusers 433fc63f6bScgdnfs 100003 nfsprog 443fc63f6bScgdmountd 100005 mount showmount 453fc63f6bScgdwalld 100008 rwall shutdown 463fc63f6bScgdsprayd 100012 spray 473fc63f6bScgdllockmgr 100020 483fc63f6bScgdnlockmgr 100021 493fc63f6bScgdstatus 100024 503fc63f6bScgdbootparam 100026 513fc63f6bScgdkeyserv 100029 keyserver 523fc63f6bScgd.Ed 533fc63f6bScgd.Sh SEE ALSO 543fc63f6bScgd.Xr getrpcent 3 55