Lines Matching +full:documentation +full:- +full:service

11 .\"    documentation and/or other materials provided with the distribution.
34 .Dq super-server
55 of its sockets, it decides what service the socket
56 corresponds to, and invokes a program to service the request.
57 The server program is invoked with the service socket
70 .Bl -tag -width indent
89 is required for each service in
92 a TCP-based service would need two entries,
104 Specify the default maximum number of times a service can be invoked
106 May be overridden on a per-service basis with the
107 "max-connections-per-ip-per-minute" parameter.
110 simultaneous invocations of each service;
112 May be overridden on a per-service basis with the "max-child"
121 Specify the maximum number of times a service can be invoked
126 simultaneous invocations of each service from a single IP address;
128 May be overridden on a per-service basis with the "max-child-per-ip"
156 .Bd -unfilled -offset indent -compact
157 service-name
158 socket-type
160 {wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]
161 user[:group][/login-class]
162 server-program
163 server-program-arguments
167 ONC RPC-based
168 service, the entry would contain these fields:
170 .Bd -unfilled -offset indent -compact
171 service-name/version
172 socket-type
174 {wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]
175 user[:group][/login-class]
176 server-program
177 server-program-arguments
183 A standard service has a well-known port assigned to it;
184 it may be a service that implements an official Internet standard or is a
185 .Bx Ns -specific
186 service.
190 well-known port assigned to them.
195 well-known port and specifies
196 the service name.
197 This feature is useful for adding locally-developed servers.
198 TCPMUX requests are only accepted when the multiplexor service itself
199 is enabled, above and beyond and specific TCPMUX-based servers; see the
203 .Em service-name
204 entry is the name of a valid service in
212 services (discussed below), the service
215 be the official name of the service (that is, the first entry in
218 ONC RPC-based
219 service, this field is a valid RPC service name listed in
227 A range is bounded by the low version to the high version -
228 .Dq rusers/1-3 .
230 .Em service-name
234 locally-chosen service name.
235 The service names listed in
244 .Em socket-type
289 service type.
306 the socket associated with the service access point, and thus whether
308 should wait for the server to exit before listening for new service
313 to the specified service address.
321 .Dq multi-threaded
328 to check for new service requests to spawn new servers.
331 .Dq single-threaded .
340 utility is an example of a multi-threaded datagram server.
342 Servers using stream sockets generally are multi-threaded and
348 and the server is given only the newly-accepted socket connected
349 to a client of the service.
350 Most stream-based services operate in this manner.
351 Stream-based servers that use
353 are started with the listening service socket, and must accept
364 service may be explicitly specified by appending a
389 invocations of each service from a single IP address by appending a
409 .Em login-class
418 .Em server-program
425 provides this service internally, this entry should
430 .Em server-program-arguments
432 .Em server-program ,
435 If the service is provided internally, the
436 .Em service-name
437 of the service (and any arguments to it) or the word
441 Currently, the only internal service to take arguments is
443 Without options, the service will always return
444 .Dq ERROR\ : HIDDEN-USER .
445 The available arguments to this service that alter its behavior are:
446 .Bl -tag -width indent
453 service is enabled
462 service is disabled,
464 This is primarily useful when running this service on a NAT machine.
506 .Dq ERROR\ : HIDDEN-USER .
518 service, as per RFC 1413.
523 Specify a timeout for the service.
544 both TCP and UDP versions; the UDP versions will refuse service if the
545 request specifies a reply port corresponding to any internal service.
553 The TCPMUX-demultiplexing service is also implemented as an internal service.
554 For any TCPMUX-based service to function, the following line must be included
557 .Bd -literal -offset indent
566 service selected and the IP-number of the remote requester if available.
627 service while no servers are available to service requests.
629 connection to such a service has been allowed,
632 over subsequent connections to the service until no more servers
638 For more information on TCP Wrappers, see the relevant documentation
643 Therefore, the service name
654 service name followed by a carriage-return line-feed <CRLF>.
656 service name is never case sensitive.
658 single character indicating positive (+) or negative (\-)
665 If the TCPMUX service name begins with a
672 The special service name
714 .Em service-name .
716 .Em service-type
765 the name of the internal service
772 service when a connection is received on that socket.
774 .Bl -tag -width /var/run/inetd.pid -compact
780 translation of service names to RPC program numbers
782 translation of service names to port numbers
836 .Bl -ohang -compact
838 .Ar service Ns / Ns Ar protocol
839 .No "server failing (looping), service terminated."
841 The number of requests for the specified service in the past minute
846 .Bl -enum -offset indent
848 There are many hosts requesting the service within a short time period.
850 A broken client program is requesting the service too frequently.
852 A malicious user is running a program to invoke the service in
853 a denial-of-service attack.
855 The invoked service program has an error that causes clients
863 Once the limit is reached, the service will be
867 .Ar service Ns / Ns Ar protocol :
870 .No service ignored
873 .Ar service Ns / Ns Ar protocol :
888 service is invoked.
891 .Ar service :
896 .Ar service :
953 .Xr imapd 8 Pq Pa ports/mail/courier-imap ,
964 .Xr telnetd 8 Pq Pa ports/net/freebsd-telnetd ,
966 .Xr uucpd 8 Pq Pa ports/net/freebsd-uucp
977 TCPMUX is based on code and documentation by Mark Lottor.
979 ONC RPC-based services is modeled after that