|
|
acl(4) -- Access Control Lists
|
|
Access Control Lists (ACLs) are supported on XFS file systems only. ACLs provide a mechanism for finer grained access control than the traditional UNIX discretionary access control mechanism. An ACL is a list of users and/or groups and their access rights, which is associated with a file or directory. ACLs are optional. In addition to the ACL used to mediate access, a directory may have a second ACL which defines the default initial ACL for files created in that directory. Files have only the si... |
|
acl_db(4) -- database of Access Control Lists
|
|
The acl_db file is used by various Xinet programs to grant (or deny) access to various subsystems. It consists of a series of named ``Access Control Lists'' that specify AppleTalk and/or IP addresses and User Accounts that are allowed to use a service. As of this writing, ACLs are used to control access to AppleShare Volumes and the configuration GUI. The file consists of a sequence of text lines, one list per line, where each line looks like: ACL_name:flags:list_item_1[,list_item_N] where ACL... |
|
dmedia/aiff(4) -- Audio Interchange File Format
|
|
The Audio File Library currently supports 13 of the commonly found audio file formats, i.e., is able to recognize, read, and write sample data and header information to and from files in these formats. It is important not to confuse sample or audio data formats with file formats. The former refers to the bit-wise organization of the sound samples in the file, i.e., whether the format is 8-bit integer or 16-bit unsigned, etc. Audio file format refers to the structure of the audio file header, the... |
|
aliases(4) -- aliases file for sendmail
|
|
This file describes user ID aliases used by /usr/sbin/sendmail. The file resides in /etc and is formatted as a series of lines of the form name: name_1, name2, name_3, . . . The name is the name to alias, and the name_n are the aliases for that name. Lines beginning with white space are continuation lines. Lines beginning with `#' are comments. Aliasing occurs only on local names. Loops can not occur, since no message will be sent to any person more than once. After aliasing has been done, loca... |
|
ar(4) -- archive (library) file format
|
|
The archive command ar combines several files into one. Archives are used mainly as libraries to be searched by the link-editor ld. A file produced by ar has a magic string at the start, followed by the constituent files, each preceded by a file header. The magic number and header layout as described in the include file are: #define ARMAG "!\n" #define SARMAG 8 #define ARFMAG "`\n" struct ar_hdr { char ar_name[16]; char ar_date[12]; char ar_uid[6]; char ar_gid[6]; char ar_mode[8]; ch... |
|
arrayd.conf(4) -- array services configuration files
|
|
The arrayd.conf and arrayd.auth files are used to describe the configuration of one or more arrays to the array services daemon. The default configuration files are "/usr/lib/array/arrayd.conf" and "/usr/lib/array/arrayd.auth", although the system administrator can override this or specify additional files. Every machine running an array services daemon (which should be every machine that is part of an array) must have its own configuration file or files. The configuration files contain info... |
|
at_log(4) -- list of errors by users of K-Talk library routines
|
|
The file at_log is a database of error messages logged by the K-Talk library. These messages give clues about the nature of error conditions encountered by the library routines. Messages are printed one per line and are created using the at_log(3) routine. |
|
autologin(4) -- set autologin user identity
|
|
/etc/autologin is an ASCII file containing the login user name to be used when autologin is enabled. The file is used by xdm(1) and clogin(1) when automatically initiating a terminal session on the graphics console. /etc/autologin.TTYLINE is like /etc/autologin except it is used by getty(1m) when initiating a terminal session for the device named by TTYLINE. For example /etc/autologin.ttyd1 will control the login processes on /dev/ttyd1.... |
|
dmedia/avr(4) -- Audio Visual Reseach File Format
|
|
The Audio File Library currently supports 13 of the commonly found audio file formats, i.e., is able to recognize, read, and write sample data and header information to and from files in these formats. It is important not to confuse sample or audio data formats with file formats. The former refers to the bit-wise organization of the sound samples in the file, i.e., whether the format is 8-bit integer or 16-bit unsigned, etc. Audio file format refers to the structure of the audio file header, the... |
|
dmedia/bicsf(4) -- Berkeley/IRCAM/CARL Sound File Format
|
|
The Audio File Library currently supports 13 of the commonly found audio file formats, i.e., is able to recognize, read, and write sample data and header information to and from files in these formats. It is important not to confuse sample or audio data formats with file formats. The former refers to the bit-wise organization of the sound samples in the file, i.e., whether the format is 8-bit integer or 16-bit unsigned, etc. Audio file format refers to the structure of the audio file header, the... |
|
bootparams(4) -- boot parameter data base
|
|
The bootparams file contains the list of client entries that diskless clients use for booting. For each diskless client the entry should contain the following information: name of client a list of keys, names of servers, and pathnames. The first item of each entry is the name of the diskless client. The subsequent item is a list of keys, names of servers, and pathnames. Items are separated by TAB or SPACE characters. Any text after the # character is ignored.... |
|
boot_cpuset(4) -- boot cpuset configuration tool
|
|
The boot_cpuset.so library provides a method for putting init(1M) into a cpuset(4). Since all "standard" processes are descendents of init, this means that all standard processes on the system (daemons, interactive, etc.) will be confined to that cpuset. The cpuset is named boot. The boot_cpuset.so library is normally installed on SGI ccNUMA systems. If it is found in /lib32 by init, it will be loaded and executed. The behaviour of the library is controlled by /etc/config/boot_cpuset and /etc/... |
|
cachefs(4) -- Cache File System Description
|
|
front file system This is the local file system on which cached data is stored. back file system This is the file system which contains the definitive copy of the data. Data is retrieved from this file system and cached on the front file system. cnode This is the internal data structure used by cachefs to manage its files. There is one cnode for each open file. Each cnode occupies 128 bytes on a 32 bit system and 256 bytes on a 64 bit system. In addition, each cnode points to a dynamically alloc... |
