|
|
|
rc.config.d(4) -- files containing system configuration information
|
|
The system configuration used at startup is contained in files within the directory /etc/rc.config.d. The file /etc/rc.config sources all of the files within /etc/rc.config.d and /etc/TIMEZONE and exports their contents to the environment. /etc/rc.config The file /etc/rc.config is a script that sources all of the /etc/rc.config.d/* scripts, and also sources /etc/TIMEZONE. To read the configuration... |
|
rcsfile(4) -- format of RCS files
|
|
An RCS file is an ASCII file. Its contents are described by the grammar below. The text is free format, i.e., spaces, tabs and newline characters have no significance except in strings. Strings are enclosed by @ symbols. If a string contains the @ symbol, the symbol must be doubled. The meta syntax uses the following conventions: | (bar) Separates alternatives. {...} (braces) Encloses optional phr... |
|
|
resolv.conf(4) -- resolver configuration file
|
|
The resolver is a set of routines in the C library (see resolver(3N)) that provide access to the Internet Domain Name System. The resolver configuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human-readable, and contains a list of keywords with values that provide various types of resolver information... |
|
resolver(4) -- resolver configuration file
|
|
The resolver is a set of routines in the C library (see resolver(3N)) that provide access to the Internet Domain Name System. The resolver configuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human-readable, and contains a list of keywords with values that provide various types of resolver information... |
|
rhosts(4) -- security files authorizing access by remote hosts and users on local host
|
|
The /etc/hosts.equiv file and files named .rhosts found in users' home directories specify remote hosts and users that are "equivalent" to the local host or user. Users from equivalent remote hosts are permitted to access a local account using rcp or remsh or to rlogin to the local account without supplying a password (see rcp(1), remsh(1), and rlogin(1)). The security provided by hosts.equiv i... |
|
rmtab(4) -- local file system mount statistics
|
|
File /etc/rmtab contains a record of all clients that mounted remote file systems from this machine. Whenever a remote mount is done, an entry is made in the rmtab file of the machine serving that file system. umount removes the entry of a remotely mounted file system. umount -a broadcasts to all servers that they should remove all entries from rmtab created by the sender of the broadcast message.... |
|
rndc.conf(4) -- rndc configuration file
|
|
The BIND utility for controlling the name server, rndc, has its own configuration file /etc/rndc.conf. This file has a structure and syntax similar to that of named's configuration file, named.conf. Statements are enclosed in braces and terminated with a semi-colon. Clauses in the statements are also semi-colon terminated. The usual comment styles supported are: C style: /* */ C++ style: // to en... |
|
rpc(4) -- rpc program number data base
|
|
File /etc/rpc contains user-readable names that can be used in place of RPC program numbers. Each line has the following information: + Name of server for the RPC program + RPC program number + Aliases Items are separated by any number of blanks and tab characters. A # anywhere in the file indicates a comment extending to the end of that line. |
|
rtradvd.conf(4) -- configuration file for router advertisement daemon
|
|
This file describes the information used by rtradvd(1M) when constructing IPv6 router advertisement packets for a specific interface as specified by RFC 2461 ("Neighbor Discovery for IP Version 6"). This file is read by rtradvd at initialization time or upon reception of signal SIGHUP. rtradvd configuration consists of two general statements (defaults, interface) and one substatement (prefixinfo... |
|
sccsfile(4) -- format of SCCS file
|
|
An SCCS file is an ASCII file consisting of six logical parts: checksum Sum of all characters in the file except the first line. delta table Contains information about each delta. user names Login names and/or numerical group IDs of users who are allowed to add deltas. flags Definitions of internal keywords. comments Arbitrary descriptive information about the file. body Actual text lines intermix... |
|
sd(4) -- all objects that Software Distributor (SD) uses, their attributes and storage formats
|
|
The SD commands create, install, distribute and manage software objects (bundles, products, subproducts and filesets). In addition, they define and manage other objects in support of the software administration tasks which users perform. This manual page describes the SD software object classes, their attributes, and the file formats used to store their definitions. For an overview of all SD comma... |
|
securenets(4) -- NIS map security file
|
|
The /etc/securenets file defines networks and hosts that may access the NIS maps on a server. Each line in the file gives a network mask and a net address, each in dotted quad format. For example: 255.255.255.255 133.33.33.33 The file may have any number of netmask/net pairs. When ypserv is started on the server, it checks for the existence of /etc/securenets and reads its contents into memory if ... |
|
security(4) -- security defaults configuration file
|
|
A number of system commands and features are configured based on certain parameters defined in the /etc/default/security configuration file. This file must be world readable and root writable. Each line in the file is treated either as a comment or as configuration information for a given system command or feature. Comments are denoted by a # at the beginning of a line. Noncomment lines are of the... |
|
services(4) -- service name data base
|
|
The file /etc/services associates official service names and aliases with the port number and protocol the services use. For each service a single line should be present with the following information: Port numbers 0 through 1023 are assigned by RFC 1700. This RFC also lists the conventional use of various ports with numbers greater tha... |
|
services.window(4) -- file containing applications and their associated memory window id
|
|
The files /etc/services.window is used by applications using memory windows. Each line in the /etc/services.window file associates an application with a memory window id. A line in the /etc/services.window file cannot start with a space or tab. The format is a unique name, defining the application, followed by a space/tab, followed by a unique window_id. See the sample file in EXAMPLES. Memory win... |
