no way to compare when less than two revisions
Diferenças
Aqui você vê as diferenças entre duas revisões dessa página.
— | espec:man-xinetd.conf [2008/06/19 16:50] (atual) – created maziero | ||
---|---|---|---|
Linha 1: | Linha 1: | ||
+ | ** mudar para português** | ||
+ | < | ||
+ | XINETD.CONF(5) | ||
+ | |||
+ | NAME | ||
+ | | ||
+ | |||
+ | DESCRIPTION | ||
+ | | ||
+ | | ||
+ | a '#' | ||
+ | |||
+ | The file contains entries of the form: | ||
+ | |||
+ | service < | ||
+ | { | ||
+ | < | ||
+ | ... | ||
+ | } | ||
+ | |||
+ | | ||
+ | The majority of attributes support only the simple | ||
+ | | ||
+ | | ||
+ | | ||
+ | these attributes will be given after all the attributes are described. | ||
+ | |||
+ | Each entry defines a service identified by the service_name. | ||
+ | | ||
+ | |||
+ | | ||
+ | vice. This | ||
+ | that can use different protocols | ||
+ | described with different entries in the configuration | ||
+ | file. | ||
+ | service name. | ||
+ | |||
+ | | ||
+ | |||
+ | RPC | ||
+ | |||
+ | INTERNAL | ||
+ | |||
+ | TCPMUX/ | ||
+ | if this is a service that will be started | ||
+ | according to the RFC 1078 protocol on the | ||
+ | TCPMUX well-known port. See the section | ||
+ | describing TCPMUX services below. | ||
+ | |||
+ | UNLISTED | ||
+ | standard system file (like / | ||
+ | RPC services, | ||
+ | RPC services). | ||
+ | |||
+ | | ||
+ | |||
+ | INTERCEPT | ||
+ | in order | ||
+ | from acceptable | ||
+ | multi-threaded | ||
+ | cepted). | ||
+ | |||
+ | NORETRY | ||
+ | failure. | ||
+ | |||
+ | IDONLY | ||
+ | end identifies the remote user (i.e. the | ||
+ | remote | ||
+ | server). | ||
+ | nection-based | ||
+ | ineffective if the USERID log option | ||
+ | not used. | ||
+ | |||
+ | NAMEINARGS | ||
+ | " | ||
+ | ing the server, as specified in " | ||
+ | This allows you to use tcpd by putting | ||
+ | tcpd in " | ||
+ | server in " | ||
+ | inetd. | ||
+ | |||
+ | NODELAY | ||
+ | NODELAY flag is set, then the TCP_NODELAY | ||
+ | flag will be set on the socket. | ||
+ | service is not a tcp service, this option | ||
+ | has no effect. | ||
+ | |||
+ | KEEPALIVE | ||
+ | KEEPALIVE flag | ||
+ | SO_KEEPALIVE | ||
+ | the socket. If the service is not a tcp | ||
+ | service, this option has no effect. | ||
+ | |||
+ | NOLIBWRAP | ||
+ | tcpwrap library to determine | ||
+ | the service. | ||
+ | to use libwrap functionality | ||
+ | able to long-running | ||
+ | xinetd; in this case, the tcpd | ||
+ | can be called | ||
+ | NAMEINARGS flag). | ||
+ | TCP transport, this flag is automatically | ||
+ | turned | ||
+ | remote | ||
+ | rpc port. | ||
+ | |||
+ | SENSOR | ||
+ | that detects | ||
+ | port. NOTE: It will NOT detect | ||
+ | scans. | ||
+ | services that you know you don' | ||
+ | When an access is made to this service' | ||
+ | port, the IP Address is added to a global | ||
+ | no_access | ||
+ | quent accesses from the originating | ||
+ | address | ||
+ | deny_time setting expires. The amount | ||
+ | time spent on this list is configurable | ||
+ | as the deny_time | ||
+ | flag will also cause xinetd to consider | ||
+ | the server attribute to be INTERNAL | ||
+ | matter | ||
+ | Another important thing to remember | ||
+ | that if the socket_type is set to stream, | ||
+ | then the wait attribute should be set to | ||
+ | no. | ||
+ | |||
+ | IPv4 | ||
+ | (AF_INET). | ||
+ | |||
+ | IPv6 | ||
+ | (AF_INET6), | ||
+ | system. | ||
+ | |||
+ | REUSE | ||
+ | vices now implicitly use the REUSE flag. | ||
+ | |||
+ | | ||
+ | the service being disabled and not starting. | ||
+ | DISABLE flag description. | ||
+ | |||
+ | | ||
+ | |||
+ | stream | ||
+ | |||
+ | dgram | ||
+ | |||
+ | raw | ||
+ | |||
+ | seqpacket | ||
+ | datagram transmission | ||
+ | |||
+ | | ||
+ | vice. | ||
+ | this attribute is not defined, the default | ||
+ | employed by the service will be used. | ||
+ | |||
+ | | ||
+ | threaded or multi-threaded and whether or not xinetd | ||
+ | accepts the connection or the server program accepts | ||
+ | the connection. If its value is yes, the service | ||
+ | single-threaded; | ||
+ | the server and then it will stop handling | ||
+ | for | ||
+ | server software will accept the connection. | ||
+ | attribute | ||
+ | and xinetd will keep handling | ||
+ | and | ||
+ | noted that udp/ | ||
+ | value to be yes since udp is not connection oriented, | ||
+ | while tcp/stream servers normally expect the value to | ||
+ | be no. | ||
+ | |||
+ | | ||
+ | attribute can either be numeric or a name. If a name | ||
+ | is given (recommended), | ||
+ | / | ||
+ | effective user ID of xinetd is not super-user. | ||
+ | |||
+ | | ||
+ | attribute can either be numeric or a name. If a name | ||
+ | is given (recommended), | ||
+ | / | ||
+ | of user will be | ||
+ | attribute is ineffective if the effective user ID of | ||
+ | xinetd is not super-user. | ||
+ | |||
+ | | ||
+ | neously active for a service (the | ||
+ | limit). The value of this attribute can be either a | ||
+ | number or UNLIMITED which means that there | ||
+ | limit. | ||
+ | |||
+ | | ||
+ | sibly negative) number; check nice(3) for more infor- | ||
+ | mation. | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | contrast to inetd, the server name | ||
+ | included in server_args. | ||
+ | |||
+ | | ||
+ | defaults to the server name, the first server_args | ||
+ | component | ||
+ | vices and the service name for redirected | ||
+ | This | ||
+ | figured with the libwrap option. | ||
+ | |||
+ | | ||
+ | service is available. | ||
+ | addresses which can be specified in any combination | ||
+ | of the following ways: | ||
+ | |||
+ | a) a numeric address in the form of %d.%d.%d.%d. If | ||
+ | the rightmost components are 0, they are treated | ||
+ | as wildcards (for example, 128.138.12.0 matches | ||
+ | all hosts on the 128.138.12 | ||
+ | | ||
+ | | ||
+ | | ||
+ | IPv4 addresses does not apply to IPv6 addresses. | ||
+ | |||
+ | b) | ||
+ | | ||
+ | | ||
+ | | ||
+ | the end of the address. | ||
+ | for IPv6 hosts. | ||
+ | |||
+ | c) a network name (from / | ||
+ | does not work for IPv6 hosts. | ||
+ | |||
+ | d) | ||
+ | | ||
+ | | ||
+ | ified host name. You may also use domain names | ||
+ | in the form of .domain.com. | ||
+ | | ||
+ | a match occurs. | ||
+ | |||
+ | e) an ip address/ | ||
+ | | ||
+ | form of 1234::/46 are also valid. | ||
+ | |||
+ | Specifying | ||
+ | service available to nobody. | ||
+ | |||
+ | | ||
+ | service is unavailable. Its value can be specified in | ||
+ | the same way as the value of the only_from attribute. | ||
+ | These | ||
+ | control enforced by xinetd. If none of the two is | ||
+ | specified | ||
+ | anyone. If both are specified for a service, the one | ||
+ | that | ||
+ | remote host determines if the service is available to | ||
+ | that | ||
+ | tains 128.138.209.0 and the no_access | ||
+ | 128.138.209.10 then the | ||
+ | 128.138.209.10 can not access the service). | ||
+ | |||
+ | | ||
+ | available. An interval has the form hour: | ||
+ | (connections will be accepted at the bounds | ||
+ | interval). | ||
+ | from 0 to 59. | ||
+ | |||
+ | | ||
+ | There are two formats: | ||
+ | |||
+ | SYSLOG syslog_facility [syslog_level] | ||
+ | The log output is sent to syslog at the speci- | ||
+ | | ||
+ | | ||
+ | lpr, news, uucp, ftp local0-7. | ||
+ | | ||
+ | ing, notice, info, debug. | ||
+ | | ||
+ | info level. | ||
+ | |||
+ | FILE | ||
+ | The log output is appended to file which will | ||
+ | be created if it does not exist. Two limits on | ||
+ | the size of the log file can be optionally | ||
+ | | ||
+ | | ||
+ | | ||
+ | the message will be sent at the alert priority | ||
+ | | ||
+ | | ||
+ | | ||
+ | then more than one service | ||
+ | | ||
+ | logs to syslog, the message will be sent at | ||
+ | the alert priority level). | ||
+ | not specified, it defaults to the soft limit | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | | ||
+ | is started and when that server exits (the service id | ||
+ | is always | ||
+ | tion of the following values may be specified: | ||
+ | |||
+ | PID | ||
+ | vice is implemented | ||
+ | forking another process the logged pro- | ||
+ | cess id will be 0) | ||
+ | |||
+ | HOST | ||
+ | |||
+ | USERID | ||
+ | the RFC 1413 identification | ||
+ | This option is available only for multi- | ||
+ | threaded stream services. | ||
+ | |||
+ | EXIT | ||
+ | with the exit status or the termination | ||
+ | signal (the process id is also logged | ||
+ | the PID option is used) | ||
+ | |||
+ | DURATION | ||
+ | |||
+ | TRAFFIC | ||
+ | redirected service. | ||
+ | |||
+ | | ||
+ | cannot be | ||
+ | resources or because of access control restrictions). | ||
+ | The | ||
+ | along with the reason for failure. | ||
+ | of the following values may be specified: | ||
+ | |||
+ | HOST | ||
+ | |||
+ | USERID | ||
+ | the RFC 1413 identification | ||
+ | This option is available only for multi- | ||
+ | threaded stream services. | ||
+ | |||
+ | ATTEMPT | ||
+ | made (this option is implied by all oth- | ||
+ | ers). | ||
+ | |||
+ | | ||
+ | version can be a single number or a range in the form | ||
+ | number-number. | ||
+ | |||
+ | | ||
+ | (this | ||
+ | unlisted). | ||
+ | |||
+ | | ||
+ | the | ||
+ | to the environment before starting a server | ||
+ | fore | ||
+ | environment plus the specified strings). | ||
+ | |||
+ | | ||
+ | variables | ||
+ | passed to the server. | ||
+ | no variables | ||
+ | itly defined using the env attribute. (notice that | ||
+ | you | ||
+ | env attribute to specify | ||
+ | will be passed to the server). | ||
+ | |||
+ | | ||
+ | specified for a service listed in / | ||
+ | must be equal to the port number listed in that file. | ||
+ | |||
+ | | ||
+ | host. When xinetd receives a tcp connection on this | ||
+ | port it spawns a process that establishes | ||
+ | tion | ||
+ | wards all data between the two hosts. | ||
+ | useful when your internal machines are not visible to | ||
+ | the | ||
+ | address) (port). | ||
+ | of the IP address in this field. | ||
+ | is performed | ||
+ | the first IP address returned is the one that is used | ||
+ | until xinetd is restarted. | ||
+ | not required when this option is specified. | ||
+ | " | ||
+ | priority. | ||
+ | |||
+ | | ||
+ | on the machine. | ||
+ | server listening on a local, secured | ||
+ | not | ||
+ | interface can do something, while the same port on a | ||
+ | different | ||
+ | ferent. Syntax: bind = (ip address of interface). | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | host | ||
+ | lished. This banner is printed regardless of access | ||
+ | control. | ||
+ | nection has been made. xinetd outputs the file as- | ||
+ | is, | ||
+ | ted for the service' | ||
+ | protocol | ||
+ | you must supply them. | ||
+ | |||
+ | | ||
+ | host | ||
+ | This banner is printed as soon as access | ||
+ | for | ||
+ | you must ensure the file is correctly | ||
+ | the | ||
+ | col requires CR-LF pairs for line termination, | ||
+ | must supply them. | ||
+ | |||
+ | | ||
+ | host when a connection to that service | ||
+ | This | ||
+ | access. This is useful for informing your users that | ||
+ | they | ||
+ | doing it anymore. | ||
+ | you | ||
+ | the service' | ||
+ | col | ||
+ | must supply them. | ||
+ | |||
+ | | ||
+ | specifies | ||
+ | source IP address. | ||
+ | defaults section. | ||
+ | |||
+ | | ||
+ | arguments. | ||
+ | nections per second to handle. If the rate of incom- | ||
+ | ing connections is higher than this, the service will | ||
+ | be temporarily disabled. | ||
+ | number of seconds to wait before re-enabling the ser- | ||
+ | vice | ||
+ | this setting | ||
+ | interval is 10 seconds. | ||
+ | |||
+ | | ||
+ | service will stop accepting connections. | ||
+ | ple: | ||
+ | nections at this load. This is the one minute load | ||
+ | average. | ||
+ | rently only Linux, Solaris, and FreeBSD are supported | ||
+ | for | ||
+ | was configured with the -with-loadavg option. | ||
+ | |||
+ | | ||
+ | is set to " | ||
+ | access to the groups that the server' | ||
+ | has | ||
+ | " | ||
+ | groups. This attribute must be set to " | ||
+ | BSD systems. | ||
+ | defaults section as well. | ||
+ | |||
+ | | ||
+ | mdns registration of services (currently only Mac OS | ||
+ | X), | ||
+ | service. | ||
+ | |||
+ | | ||
+ | octal value. | ||
+ | " | ||
+ | xinetd sets its own umask to the previous umask OR'd | ||
+ | with 022. This is the umask that will be | ||
+ | by all child processes | ||
+ | used. | ||
+ | |||
+ | | ||
+ | enable only the services listed as arguments to this | ||
+ | attribute; | ||
+ | ftp | ||
+ | ID' | ||
+ | the ID. It might accidentally be the ID, but you bet- | ||
+ | ter check.) Note that the service " | ||
+ | and | ||
+ | enabled despite being listed in this attribute. | ||
+ | |||
+ | | ||
+ | / | ||
+ | new configuration file. It is not the same thing as | ||
+ | pasting the file into xinetd.conf where the include | ||
+ | directive is given. | ||
+ | same | ||
+ | from within a service. It must be specified | ||
+ | a service declaration. | ||
+ | |||
+ | | ||
+ | / | ||
+ | excluding | ||
+ | ending with a tilde (' | ||
+ | configuration | ||
+ | alphabetical order according to the C locale. This | ||
+ | allows you to specify services one per file within a | ||
+ | directory. | ||
+ | ified from within a service declaration. | ||
+ | |||
+ | | ||
+ | vice. One parameter is required, which is | ||
+ | positive | ||
+ | set the limit to (K or M may be used to specify kilo- | ||
+ | bytes/ | ||
+ | Linux' | ||
+ | to set this limit than rlimit_data, | ||
+ | rlimit_stack. This resource limit is only implemented | ||
+ | on Linux systems. | ||
+ | |||
+ | | ||
+ | vice may use. One parameter is required, | ||
+ | either a positive integer representing the number of | ||
+ | CPU seconds limit to, or " | ||
+ | |||
+ | | ||
+ | service. | ||
+ | a positive integer representing the number | ||
+ | or " | ||
+ | |||
+ | | ||
+ | vice. | ||
+ | likely candidate for swapping out to disk when memory | ||
+ | is low. One parameter is required, which is either a | ||
+ | positive | ||
+ | " | ||
+ | |||
+ | | ||
+ | One parameter is required, which is either a positive | ||
+ | integer representing the number of bytes or " | ||
+ | ITED" | ||
+ | |||
+ | | ||
+ | IP addresses are denied to someone that sets off the | ||
+ | SENSOR. The unit of time | ||
+ | options are: FOREVER, NEVER, | ||
+ | FOREVER causes the IP address not to be purged until | ||
+ | xinetd is restarted. NEVER has the | ||
+ | logging the offending IP address. | ||
+ | value would be 60 minutes. This should stop most DOS | ||
+ | attacks while allowing IP addresses that come from a | ||
+ | pool to be recycled | ||
+ | option must | ||
+ | flag. | ||
+ | |||
+ | You don't need to specify all of the above attributes | ||
+ | | ||
+ | |||
+ | socket_type | ||
+ | user (non-internal services only) | ||
+ | server (non-internal services only) | ||
+ | wait | ||
+ | protocol (RPC and unlisted services only) | ||
+ | rpc_version (RPC services only) | ||
+ | rpc_number (unlisted RPC services only) | ||
+ | port (unlisted non-RPC services only) | ||
+ | |||
+ | The following attributes support all assignment operators: | ||
+ | |||
+ | only_from | ||
+ | no_access | ||
+ | log_on_success | ||
+ | log_on_failure | ||
+ | passenv | ||
+ | env (does not support the ' | ||
+ | |||
+ | | ||
+ | The remaining attributes support only the ' | ||
+ | at most once in a service entry. | ||
+ | |||
+ | | ||
+ | has the form | ||
+ | |||
+ | defaults | ||
+ | { | ||
+ | < | ||
+ | ... | ||
+ | } | ||
+ | |||
+ | This entry provides default attribute values for service entries that | ||
+ | | ||
+ | |||
+ | log_type (cumulative effect) | ||
+ | bind | ||
+ | per_source | ||
+ | umask | ||
+ | log_on_success (cumulative effect) | ||
+ | log_on_failure (cumulative effect) | ||
+ | only_from (cumulative effect) | ||
+ | no_access (cumulative effect) | ||
+ | passenv (cumulative effect) | ||
+ | instances | ||
+ | disabled (cumulative effect) | ||
+ | enabled (cumulative effect) | ||
+ | banner | ||
+ | banner_success | ||
+ | banner_fail | ||
+ | per_source | ||
+ | groups | ||
+ | cps | ||
+ | max_load | ||
+ | |||
+ | Attributes | ||
+ | multiple times | ||
+ | with the values specified each time accumulating (i.e. ' | ||
+ | the same thing as ' | ||
+ | all have the same meaning as if they were specified in a ser- | ||
+ | vice entry. | ||
+ | even if they | ||
+ | allows for quick reconfiguration by specifying | ||
+ | vices with the disabled attribute instead of commenting them | ||
+ | out. The value of this attribute is a list of space separated | ||
+ | service ids. enabled has the same properties as disabled. | ||
+ | difference being that enabled is a list of which services | ||
+ | to be enabled. If enabled | ||
+ | specified are available. If enabled is not specified, all ser- | ||
+ | vices are assumed | ||
+ | abled. | ||
+ | |||
+ | |||
+ | INTERNAL SERVICES | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | for them. Those ones (time, | ||
+ | | ||
+ | |||
+ | |||
+ | TCPMUX Services | ||
+ | | ||
+ | vices may not have a well-known port associated with them, and can be | ||
+ | | ||
+ | |||
+ | For each service that is to be accessed via TCPMUX, a service entry in | ||
+ | / | ||
+ | must exist. | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | vice requestor first makes the connection | ||
+ | | ||
+ | | ||
+ | with some form of organization ID. | ||
+ | |||
+ | The type field can be either TCPMUX or TCPMUXPLUS. If the type is TCP- | ||
+ | | ||
+ | | ||
+ | If the type is TCPMUX, the server that is started is responsible | ||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | / | ||
+ | |||
+ | | ||
+ | must be tcp. | ||
+ | |||
+ | | ||
+ | |||
+ | service myorg_server | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | service tcpmux | ||
+ | { | ||
+ | | ||
+ | id = tcpmux | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | NOTES | ||
+ | | ||
+ | tion: socket_type, | ||
+ | |||
+ | | ||
+ | a service (either directly or via defaults) the address | ||
+ | | ||
+ | |||
+ | | ||
+ | and not on its domain address. We do this so that we can avoid | ||
+ | | ||
+ | | ||
+ | | ||
+ | down side of this scheme is that if the IP address of | ||
+ | host changes, then access to that host may be denied until xinetd | ||
+ | is reconfigured. | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | | ||
+ | does not run an identification server or the server sends back a | ||
+ | bad reply, access will not be denied unless the IDONLY | ||
+ | flag is used. | ||
+ | |||
+ | | ||
+ | | ||
+ | has a performance impact so it is up to you to make the compromise | ||
+ | | ||
+ | | ||
+ | the time overhead-per-datagram for a UDP-based service using vari- | ||
+ | | ||
+ | width reduction because of interception while sending | ||
+ | | ||
+ | same as for UDP-based services but it is " | ||
+ | | ||
+ | given in the table as system_callsxdata_sent_per_call, | ||
+ | | ||
+ | width reduction is given in terms of bytes per second | ||
+ | | ||
+ | All measurements were done on a SparcStation | ||
+ | 4.1. | ||
+ | |||
+ | Datagram size (bytes) | ||
+ | --------------------- | ||
+ | 64 1.19 | ||
+ | 256 | ||
+ | 1024 | ||
+ | 4096 | ||
+ | |||
+ | |||
+ | Bytes sent | ||
+ | ---------- | ||
+ | 10000x64 | ||
+ | 10000x256 | ||
+ | 10000x1024 | ||
+ | 10000x4096 | ||
+ | |||
+ | EXAMPLE | ||
+ | # | ||
+ | # Sample configuration file for xinetd | ||
+ | # | ||
+ | |||
+ | defaults | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | # | ||
+ | # Note 1: the protocol attribute is not required | ||
+ | # Note 2: the instances attribute overrides the default | ||
+ | # | ||
+ | service login | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | # | ||
+ | # Note 1: the instances attribute overrides the default | ||
+ | # Note 2: the log_on_success flags are augmented | ||
+ | # | ||
+ | service shell | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | service ftp | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | # Limit telnet sessions to 8 Mbytes of memory and a total | ||
+ | # 20 CPU seconds for child processes. | ||
+ | service telnet | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | # | ||
+ | # This entry and the next one specify internal services. Since | ||
+ | # this is the same service using a different socket type, the | ||
+ | # id attribute is used to uniquely identify each entry | ||
+ | # | ||
+ | service echo | ||
+ | { | ||
+ | id = echo-stream | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | service echo | ||
+ | { | ||
+ | id = echo-dgram | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | # | ||
+ | # Sample RPC service | ||
+ | # | ||
+ | service rstatd | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | env = LD_LIBRARY_PATH=/ | ||
+ | } | ||
+ | |||
+ | # | ||
+ | # Sample unlisted service | ||
+ | # | ||
+ | service unlisted | ||
+ | { | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | } | ||
+ | |||
+ | SEE ALSO | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | M. Lottor, TCP Port Service Multiplexer (TCPMUX), RFC 1078 Nov 1988 | ||
+ | | ||
+ | |||
+ | BUGS | ||
+ | | ||
+ | the remote host is not performed when wait is yes and socket_type | ||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | the remote host. | ||
+ | |||
+ | | ||
+ | the remote host for services where wait is | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | There is no way to put a SPACE in an environment variable. | ||
+ | |||
+ | | ||
+ | | ||
+ | |||
+ | The INTERCEPT flag is not supported for internal services | ||
+ | | ||
+ | |||
+ | 14 June 2001 | ||
+ | </ |