|
|
|
pppoerd.conf(4) -- PPPoE (Point to Point Protocol over Ethernet) relay configuration file
|
|
pppoerd.conf is the configuration file for the pppoerd daemon. This file is read by pppoerd to initailize the relay. The default file is /etc/ppp/pppoerd.conf. Note that, you cannot run pppoerd without this configuration file. Each entry in the pppoerd.conf file is separated by a new line. Blank lines and lines that begin with # are ignored. |
|
pppoesd.conf(4) -- PPPoE (Point to Point Protocol over Ethernet) server configuration file
|
|
pppoesd.conf is the configuration file for the pppoesd daemon. This file is read by pppoesd to initialize the server. The default file is /etc/ppp/pppoesd.conf. You can use this file to set parameters for each network interface used by pppoesd during PPPoE sessions. Each entry in the pppoesd.conf file is of the following format: parameter=value Each entry in the configuration file is separated by ... |
|
|
privgrp(4) -- format of privileged values
|
|
setprivgrp() sets a mask of privileges, and getprivgrp(2) returns an array of structures giving privileged group assignments on a pergroup-ID basis (see getprivgrp(2)). setprivgrp() associates a kernel capability with a group ID. This allows subletting of superuser-like privileges to members of a particular group or groups. The constants and structures needed for these system calls are defined in ... |
|
profile(4) -- set up user's environment at login time
|
|
If the file /etc/profile exists, it is executed by the shell for every user who logs in. The file /etc/profile should be set up to do only those things that are desirable for every user on the system, or to set reasonable defaults. If a user's login (home) directory contains a file named .profile, that file is executed (via the shell's exec .profile) before the session begins. .profile files are... |
|
proto(4) -- prototype job file for at(1)
|
|
When a job is submitted to at or batch, the job is constructed as a POSIX shell script (see at(1)). The job file is created in /var/spool/cron/atjobs as follows: + at creates a header describing the job as an at job or a batch job. at jobs submitted to all queues other than queue a are listed as batch jobs. The header is: : at job for an at job, or : batch job for a batch job. + A set of POSIX she... |
|
protocols(4) -- protocol name data base
|
|
This file associates protocol numbers with official protocol names and aliases. This allows the user to refer to a protocol by a symbolic name instead of a number. For each protocol a single line should be present with the following information: These mappings are defined in RFC 1700 Assigned Numbers. Aliases are other names under which... |
|
prpwd(4) -- protected password authentication database files used for trusted systems
|
|
An authentication profile is maintained for each user on the system. A user profile is kept in a protected password database file that is accessible only to the System Administrator. The protected password database files contain among other things the encrypted password for the user account. On a trusted system, the passwords are hidden from normal users. The protected password database files do n... |
|
publickey(4) -- public key database
|
|
/etc/publickey is a local public key database that is used for secure RPC. The /etc/publickey file can be used in conjunction with or instead of other publickey databases, including the NIS publickey map and the NIS+ publickey map. Each entry in the database consists of a network user name (which may refer to either a user or a hostname), followed by the user's public key (in hex notation), a col... |
|
queuedefs(4) -- queue description file for at, batch, and crontab
|
|
The queuedefs file describes the characteristics of the queues managed by cron (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[.[njobj][j][nicen][n][nwaitw] The fields in this line are: w] The fields in this line are: q The name of the queue, such that a is the default queue for jobs started by at (see at(1)), b is the queue for jo... |
|
rc.config(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... |
|
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... |
