1rpcbind(1M)             System Administration Commands             rpcbind(1M)
2
3
4

NAME

6       rpcbind - universal addresses to RPC program number mapper
7

SYNOPSIS

9       rpcbind [-d] [-w]
10
11

DESCRIPTION

13       rpcbind  is  a  server that converts RPC program numbers into universal
14       addresses. It must be running on the host to be able to make RPC  calls
15       on a server on that machine.
16
17
18       When  an  RPC service is started, it tells rpcbind the address at which
19       it is listening, and the RPC program numbers it is prepared  to  serve.
20       When  a client wishes to make an RPC call to a given program number, it
21       first contacts rpcbind on the server machine to determine  the  address
22       where RPC requests should be sent.
23
24
25       rpcbind should be started before any other RPC service. Normally, stan‐
26       dard RPC servers are started by  port  monitors,  so  rpcbind  must  be
27       started before port monitors are invoked.
28
29
30       When  rpcbind is started, it checks that certain name-to-address trans‐
31       lation-calls function correctly. If they fail, the  network  configura‐
32       tion  databases can be corrupt. Since RPC services cannot function cor‐
33       rectly in this situation, rpcbind reports the condition and terminates.
34
35
36       rpcbind maintains an open transport end for each transport that it uses
37       for indirect calls. This is the UDP port on most systems.
38
39
40       The  rpcbind  service  is  managed  by the service management facility,
41       smf(5), under the service identifier:
42
43         svc:/network/rpc/bind
44
45
46
47
48       Administrative actions on this service, such as enabling, disabling, or
49       requesting restart, can be performed using svcadm(1M). rpcbind can only
50       be started by the superuser or someone  in  the  Primary  Administrator
51       role.
52
53
54       The  configuration properties of this service can be modified with svc‐
55       cfg(1M).
56
57
58       The following SMF property is used  to  allow  or  disallow  access  to
59       rpcbind by remote clients:
60
61         config/local_only = true
62
63
64
65       The  default value, true, shown above, disallows remote access; a value
66       of false allows remove access. See EXAMPLES.
67
68
69       The FMRI svc:network/rpc/bind property group config contains  the  fol‐
70       lowing property settings:
71
72       enable_tcpwrappers    Specifies  that the TCP wrappers facility is used
73                             to control access to TCP services. The value true
74                             enables   checking.   The   default   value   for
75                             enable_tcpwrappers is false. If  the  enable_tcp‐
76                             wrappers  parameter is enabled, then all calls to
77                             rpcbind originating from non-local addresses  are
78                             automatically  wrapped by the TCP wrappers facil‐
79                             ity. The syslog facility code daemon is  used  to
80                             log  allowed connections (using the info severity
81                             level) and  denied  traffic  (using  the  warning
82                             severity   level).   See   syslog.conf(4)  for  a
83                             description of syslog codes and severity  levels.
84                             The  stability level of the TCP wrappers facility
85                             and its configuration files is External.  As  the
86                             TCP  wrappers  facility is not controlled by Sun,
87                             intrarelease incompatibilities are not  uncommon.
88                             See attributes(5).
89
90
91       verbose_logging       Specifies  whether the TCP wrappers facility logs
92                             all calls orjust the denied calls. The default is
93                             false.  This option has no effect if TCP wrappers
94                             are not enabled.
95
96
97       allow_indirect        Specifies whether rpcbind allows  indirect  calls
98                             at  all. By default, rpcbind allows most indirect
99                             calls,  except  to  a  number  of  standard  ser‐
100                             vices(keyserv, automount, mount, nfs, rquota, and
101                             selected NIS  and  rpcbind  procedures).  Setting
102                             allow_indirect to false causes all indirect calls
103                             to be dropped. The default is true. NIS broadcast
104                             clients   rely   on  this  functionality  on  NIS
105                             servers.
106
107

OPTIONS

109       The following options are supported:
110
111       -d    Run in debug mode. In this mode, rpcbind does not  fork  when  it
112             starts.  It  prints  additional information during operation, and
113             aborts on certain errors. With this option,  the  name-to-address
114             translation consistency checks are shown in detail.
115
116
117       -w    Do  a  warm  start.  If rpcbind aborts or terminates on SIGINT or
118             SIGTERM, it writes the current list  of  registered  services  to
119             /var/run/portmap.file and /var/run/rpcbind.file. Starting rpcbind
120             with the -w option instructs it to look for these files and start
121             operation  with  the  registrations  found  in  them. This allows
122             rpcbind to resume operation without requiring all RPC services to
123             be restarted.
124
125

EXAMPLES

127       Example 1 Allowing Remote Access
128
129
130       The following sequence of commands allows remote access to rpcbind.
131
132
133         # svccfg -s svc:/network/rpc/bind setprop config/local_only = false
134         # svcadm refresh svc:/network/rpc/bind
135
136
137

FILES

139       /var/run/portmap.file    Stores the information for RPC services regis‐
140                                tered over IP based transports for warm  start
141                                purposes.
142
143
144       /var/run/rpcbind.file    Stores  the information for all registered RPC
145                                services for warm start purposes.
146
147

ATTRIBUTES

149       See attributes(5) for descriptions of the following attributes:
150
151
152
153
154       ┌─────────────────────────────┬─────────────────────────────┐
155       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
156       ├─────────────────────────────┼─────────────────────────────┤
157       │Availability                 │SUNWcsu                      │
158       ├─────────────────────────────┼─────────────────────────────┤
159       │Interface Stability          │See below.                   │
160       └─────────────────────────────┴─────────────────────────────┘
161
162
163       TCP wrappers is External.
164

SEE ALSO

166       smf(5),  rpcinfo(1M),  svcadm(1M),  svccfg(1M),   rpcbind(3NSL),   sys‐
167       log.conf(4), attributes(5), smf(5)
168
169
170       For  information  on the TCP wrappers facility, see the hosts_access(4)
171       man page, delivered as part of the  Solaris  operating  environment  in
172       /usr/sfw/man and available in the SUNWtcpd package.
173

NOTES

175       Terminating  rpcbind  with  SIGKILL  prevents the warm-start files from
176       being written.
177
178
179       All RPC servers are restarted if the following occurs: rpcbind  crashes
180       (or  is  killed  with SIGKILL) and is unable to to write the warm-start
181       files; rpcbind is started without the -w option after a graceful termi‐
182       nation. Otherwise, the warm start files are not found by rpcbind.
183
184
185
186SunOS 5.11                        1 Aug 2006                       rpcbind(1M)
Impressum