|
|
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... |
|
capabilities(4) -- Capability Mechanism
|
|
The capability mechanism provides fine grained control over the privileges of a process. As a process attribute, a capability allows the process to perform a specific set of restricted operations, without granting general override of the system's protection scheme. A process can possess multiple capabilities. Collectively, all defined capabilities comprise the set of abilities that are traditionally associated with the root user. Defined capabilities are: CAP_ACCT_MGT Privilege to use accountin... |
|
capability(4) -- user capability database
|
|
Here is a sample /etc/capability file: root:all+eip:all+eip sysadm:all=:all= cmwlogin:all+eip:all+eip diag:all=:all= daemon:all=:all= bin:all=:all= uucp:all=:all= sys:all=:all= adm:all=:all= lp:all=:all= nuucp:all=:all= auditor:CAP_AUDIT_WRITE,CAP_AUDIT_CONTROL,CAP_KILL+eip:CAP_AUDIT_WRITE,CAP_AUDIT_CONTROL,CAP_KILL+eip dbadmin:all=:all= xserver:all=:all= demos:all=:all= tutor:all=:all= guest:all=:all= jenny:all=:CAP_DAC_READ_SEARCH+eip Page 1 capability(4) capability(4) In this example, there a... |
|
dmedia/cdframe(4) -- structure of a frame of audio data on Compact Disc (CD)
|
|
Audio on Compact Discs (CD) is blocked into frames. The CD has 75 frames each second. One frame of data contains both audio and non-audio data (known as subcodes). These frames are frequently referred to as subcode-frames because it takes one complete frame to assemble all the bits of a chunk of subcode. A program reading a CD in audio mode must read a minimum of one CD frame. This is enforced by the function CDreadda(3) in libcdaudio. The cdframe structure, describing the content of a frame of ... |
|
cftime(4) -- language specific strings
|
|
/lib/cftime/usa_english Jan Feb ... January February ... Sun Mon ... Sunday Monday ... %H:%M:%S %m/%d/%y %a %b %d %T %Z %Y AM PM Page 1 CFTIME(4) CFTIME(4) |
|
clearance(4) -- user clearance label information file
|
|
Here is a example /etc/clearance file : Betty:adminlabel midlabel...highlabel lowlabel Bubba:lowlabel midlabel adminlabel Bubbles:lowlabel...midlabel highlabel...adminlabel Betty is cleared for lowlabel, the label range from midlabel to highlabel, and adminlabel. Bubba is cleared for lowlabel, midlabel and adminlabel only (notice no clearance ranges). Bubbles is cleared for the security ranges between lowlabel to midlabel and highlabel to adminlabel. duck:userlow:userlow dblow...dblow bill:userl... |
|
core(4) -- format of core image file
|
|
The IRIX system writes out a core image of a terminated process when any of various errors occur. See signal(2) for the list of reasons; the most common are memory violations, illegal instructions, bus errors, and user-generated quit signals. The core image is called core and is written in the process's working directory (provided it can be; normal access controls apply). A process with an effective user ID different from the real user ID does not produce a core image. The format of the core im... |
|
cpio(4) -- format of cpio archive
|
|
cpio(1), find(1), stat(2) PPPPaaaaggggeeee 1111 |
|
cpuset(4) -- cpuset configuration files
|
|
The following configuration file describes an exclusive cpuset containing 4 CPUs: #cpuset configuration file EXCLUSIVE MEMORY_LOCAL MEMORY_EXCLUSIVE |
|
cshrc(4) -- system-wide csh initialization command file
|
|
/etc/cshrc |
|
cvprc(4) -- file describing WorkShop performance tasks
|
|
Lines beginning with # are comments. Blank lines are also allowed. A task line begins with the task name, followed immediately by a colon. The remainder of the line is cvp arguments, exactly as they would be specified to cvp, except that the -T argument is silently ignored. |
|
X11/cvt_fun_tbl(4) -- Function key conversion table of Input Manager of the X Window System Version 11 (xwnmo(1X))
|
|
Converts a function key code(KeySym) generated by XLookupString() to a one-byte character(Wnn code) according to preset data. Coding format: [ KeySym-entry Wnn-code ] Lines that start with a semicolon (;) are comments. Code notation: 0?? ---> Octal 0x?? or 0X?? ---> Hexadecimal ?? ---> Decimal |
|
X11/cvt_meta_tbl(4) -- Meta key conversion table of Input Manager of the X Window System Version 11 (xwnmo(1X))
|
|
Converts a meta key code(KeySym) generated by XLookupString() to a one-byte character(Wnn code) according to preset data. Coding format: [ KeySym-entry Wnn-code ] Lines that start with a semicolon (;) are comments. Code notation: 0?? ---> Octal 0x?? or 0X?? ---> Hexadecimal ?? ---> Decimal |
|
X11/cvt_xim_tbl(4) -- key conversion table of Input Manager of the X Window System Version 11 (xwnmo(1X))
|
|
Converts a key code(KeySym) generated by XLookupString() to a one-byte character(Wnn code) according to preset data. Coding format: [ State-or-KeySym Wnn-code ] State-or-KeySym = [States]KeySym-name States = State-name'|'[States] Lines that start with a semicolon (;) are comments. KeySym-name is a string declared in keysymdef.h (except the prefix "XA_"). State-name is one between the following string. "Shift" ---> means ShiftMask "Ctrl" ---> means ControlMask "Meta" -... |
|
dmedia/datframe(4) -- structure of a frame of audio data on Digital Audio Tape (DAT)
|
|
The Digital Audio Tape (DAT) recorder system is very complex. This man page gives the most useful and relevant information for DAT use in professional systems. It is by no means comprehensive. Conflicts and questions must be resolved by reference to the definitive DAT Conference specification referenced below. Audio on Digital Audio Tapes (DAT) is blocked into frames. A DAT recording has 33.33 frames every second. One frame of data contains both audio and non-audio data (known as subcodes). A pr... |
|
dbg(4) -- the debug filesystem
|
|
mntproc(1M), proc(4). PPPPaaaaggggeeee 1111 |
|
defaultPrivileges(4) -- default system administration privileges
|
|
The files in /var/sysadm/defaultPrivileges should not be edited directly. Use the addpriv(1M) and rmpriv(1M) commands to administer default privileges. |
|
dir(4) -- format of EFS directories
|
|
A directory behaves exactly like an ordinary file, save that no user may write into a directory. The fact that a file is a directory is indicated by a bit in the flag word of its i-node entry [see inode(4)]. The EFS directory format supports variable length names of up to 255 characters. |
|
dirent(4) -- file system independent directory entry
|
|
Different file system types may have different directory entries. The dirent structure defines a file system independent directory entry, which contains information common to directory entries in different file system types. A set of these structures is returned by the getdents(2) system call. The dirent structure is defined below. struct dirent { ino_t d_ino; off_t d_off; unsigned short d_reclen; char d_name[1]; }; The d_ino is a number which is unique for each file in the file system. The fiel... |
|
dmedia/dmbuffer(4) -- Digital Media data transport subsystem
|
|
The DMbufferpool and DMbuffer data types and operations on them implement the Digital Media data transport subsystem. This subsystem is for sharing and exchanging time sensitive visual data between compression devices and algorithms, video input/output, graphics rendering and texturing, and the host processor(s). An overview of the DMbufferpool and DMbuffer data types is presented here along with brief descriptions of their defined operations within the data transport subsystem as well as in the... |
|
dmedia/dmic(4) -- Digital Media image conversion and compression
|
|
The DMimageconverter data type and its operations implement the Digital Media image converter subsystem. This is a framework which supports a variety of compression and decompression devices and algorithms video rate JPEG and MPEG. NOTE: Some realtime compression devices are available only as extra optional products. The DMimageconverter data type represents an image converter context which performs a specific image conversion. The image conversion is principally a specific compression or decomp... |
|
dwarf(4) -- dwarf version 2 debugging information format
|
|
DWARF is a format for the information generated by compilers, assemblers, and linkage editors that is necessary for source-level debugging. It allows a compact representation of programs in many languages and is easily extended to handle additional languages and individual compiler/debugger requirements. Consumers reading DWARF information they do not understand are able to easily skip past that information, meaning that older consumers are not broken by the addition of new features. DWARF itsel... |
|
efs(4) -- layout of the Extent File System
|
|
An Extent File System can reside on a regular disk partition or on a logical volume; see lv(1M). The disk partition or volume is divided into a certain number of 512-byte sectors, also called basic blocks. The current maximum size limit of an Extent File System is 16777214 blocks, equivalent to 8 gigabytes. The Extent File System imposes a common format for certain vital information on its underlying storage medium. Basic block 0 is unused and is available to contain a bootstrap program or other... |
|
elf(4) -- Executable and Linking Format (ELF) files
|
|
The file name a.out is the default ELF-format output file name from the link editor ld(1). The link editor will make an a.out executable if there were no errors and no unresolved external references. Programs that manipulate ELF files may use the library described in elf(3E). An overview of the file format follows. For more complete information, see the references given below. Linking View Execution View ELF header ELF header Program header table Program header table (optional) Section 1 Segment... |
|
ethers(4) -- ethernet address to hostname database
|
|
/etc/ethers |
|
exports(4) -- list of NFS filesystems being exported
|
|
The file /etc/exports describes the filesystems that are being exported to NFS clients. It is created by the system administrator using a text editor It is processed by exportfs(1M) at system startup and by the mount request daemon, mountd(1M), each time a mount request is received. exportfs should be re-executed after making changes to the file. The file consists of a list of filesystems, the netgroup(4) or machine names allowed to remote mount each filesystem and possibly a list of options. Th... |
|
fd(4) -- file descriptor files
|
|
open(2), dup(2) |
|
filesystems(4) -- IRIX filesystem types
|
|
The nfs and kfs filesystems are optional products. Support for iso9660 filesystems is in the optional subsystem eoe.sw.cdrom. IRIX implements dos, hfs, iso9660, and kfs filesystems as user mode NFS daemons. In some cases errors detected by these daemons are reported as NFS errors. Although NFS is a product option, support for these filesystem types is not dependent on the installation of NFS. Page 2 filesystems(4) filesystems(4)... |
|
filetype(4) -- K-AShare's filetype specification file
|
|
The katype(1) and ksd(1m) commands identify the type of a file using, among other tests, a test for whether the file begins with a certain magic number. The file /usr/adm/appletalk/filetype specifies the magic numbers and other test being applied. The tests determine the proper type of the native UNIX files for the Macintosh AFP client. Each line of the file specifies a test to be performed. A test compares the data starting at a particular offset in the file with a 1-byte, 2-byte, or 4-byte num... |
|
fsd.auto(4) -- table of device special files for daemons to monitor
|
|
The /etc/fsd.auto file below causes mediad to do the following on system startup: check the floppy at /dev/rdsk/fds0d3.3.5hi for floppy insertions once every 2 seconds and hardware floppy ejects once every 60 seconds; check the CDROM at /dev/scsi/sc0d4l0 at the default intervals; and do not check the tape device at /dev/tape. /dev/rdsk/fds0d3.3.5hi /floppy mediad rw,inschk=2,rmvchk=60 0 0 /dev/scsi/sc0d4l0 /CDROM mediad ro 0 0 /dev/tape /tape mediad mon=off 0 0... |
|
fsd.tab(4) -- table of daemons spawned from /etc/fsd.auto
|
|
An /etc/fsd.auto file that shows mediad is running for the floppy at /dev/rdsk/fds0d3.3.5hi and the cdrom at /dev/scsi/sc0d4l0 but not for the device at /dev/tape would look like the following. /dev/rdsk/fds0d3.3.5hi /flop dos rw,sock=/tmp/.mediada001UI 0 0 /dev/scsi/sc0d4l0 /CDROM iso9660 ro,sock=/tmp/.mediada001UI 0 0 |
|
fspec(4) -- format specification in text files
|
|
ed(1), newform(1), tabs(1) PPPPaaaaggggeeee 2222 |
|
fstab(4) -- static information about filesystems
|
|
The filesystem types nfs2, nfs3, and nfs3pref are accepted for compatibility with earlier releases. nfs2 is equivalent to vers=2. nfs3 is equivalent to vers=3. nfs3pref is equivalent to nfs with no vers= option. Options used by the mount(1M) command on normal filesystems are ignored when applied to the root filesystem, since the fstab file cannot be read before mounting the root filesystem. These options include rw and ro (the root filesystem cannot be mounted read-only), grpid, quota and qnoenf... |
|
gettydefs(4) -- speed and terminal settings used by getty
|
|
/etc/gettydefs |
|
grio_disks(4) -- description of guaranteed I/O rates for disk devices
|
|
/etc/grio_disks |
|
group(4) -- group membership file
|
|
/etc/group |
|
hosts(4) -- trusted hosts by system and by user
|
|
The owner of the .rhosts file must be the super-user (i.e., root) or the user in whose home directory it resides. The contents of a user's .rhosts file will be disregarded if it is owned by another user or if its permissions allow anyone who is not the owner to modify the file. Use the chmod(1) command to add the proper protection: chmod 600 .rhosts Likewise, /etc/hosts.equiv must be owned by and writable only by the super-user. HOSTS.EQUIV(4) HOSTS.EQUIV(4) If the user's home directory is NFS... |
|
hosts.equiv(4) -- trusted hosts by system and by user
|
|
The owner of the .rhosts file must be the super-user (i.e., root) or the user in whose home directory it resides. The contents of a user's .rhosts file will be disregarded if it is owned by another user or if its permissions allow anyone who is not the owner to modify the file. Use the chmod(1) command to add the proper protection: chmod 600 .rhosts Likewise, /etc/hosts.equiv must be owned by and writable only by the super-user. Page 2 HOSTS.EQUIV(4) HOSTS.EQUIV(4) If the user's home directory... |
|
hwgraph(4) -- hardware graph and hardware graph file system
|
|
The internal hardware graph is exported to user-level through a pseudofile system (similar to /proc(4)). The hwgfs file system represents the collection of all interesting hardware and pseudo-devices as a file system tree of special files and directories. It is mounted at /hw by the kernel during system boot, and can be re-mounted using /etc/mnthwgfs. In order to represent the directed graph as a Unix file system tree, hwgfs imposes an artificial hierarchy on the hardware graph, and it uses hard... |
|
dmedia/iff(4) -- Amiga IFF/8SVX Audio 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... |
|
inittab(4) -- script for the init process
|
|
/etc/inittab |
|
inode(4) -- format of an Extent File System inode
|
|
An inode is the volume data structure used by the Extent File System (EFS) to implement the abstraction of a file. (This is not to be confused with the in-core inode used by the operating system to manage memory-resident EFS files.) An inode contains the type (for example, plain file, directory, symbolic link, or device file) of the file; its owner, group, and public access permissions; the owner and group ID numbers; its size in bytes; the number of links (directory references) to the file; and... |
|
intro(4) -- introduction to file formats
|
|
|
|
dmedia/jpeg(4) -- JPEG compression format
|
|
The JPEG compression format is supported by several developer and enduser products. |
|
ldap.conf(4) -- Lightweight Directory Access Protocol configuration file
|
|
This file controls the behavior of the Lightweight Directory Access Protocol (LDAP) client implementation for nsd. It is read by the initialization routine of the ldap(7P) library when the nsd daemon is started, or sent the SIGHUP signal. This file contains information about remote LDAP daemons database schemas, and format rules. The file is made up of comment lines, table entries, server entries and the domain command. Comment lines begin with either a '#' or a ';' character, and are ignore... |
|
libdwarf(4) -- dwarf debugging information format library interface
|
|
Because the dwarf version 2 debugging information format uses several techniques to offer descriptive power and flexibility while retaining a compact representation, reading and writing the data is not simple. Consequently two C interfaces are provided. A consumer interface that allows easy reading of all the data, hiding representation details while providing all the data in the debugging information. See A Consumer Library Interface to DWARF, which is in troff in libdwarf2.1.mm and PostScript ... |
|
limits(4) -- file headers for implementation-specific constants
|
|
The header files and is a list of various limits on resources that IRIX imposes on applications. The limits in these headers fall into 3 main categories. Numerical limits These specify the maximum and minimum representable numbers for the fundamental "C" types (integer, float, etc.). Minimum resource limits These specify the minimum limits on certain resources. These are usually specified by either the POSIX or XPG standards. Many of these have higher actual limits that ar... |
|
linenum(4) -- line number entries in an object file
|
|
The cc(1), f77(1), pc(1), and pl1(1) commands generate an entry in the object file for each source line on which a breakpoint is possible [when any of the commands are invoked with the -g option]. Users can then reference line numbers when using dbx (see dbx(1)). The structure of these line number entries is described in the Assembly Language Programmer's Guide. |
|
llc2template(4) -- Description of LLC2 configuration file
|
|
lltune(1M). PPPPaaaaggggeeee 2222 |
|
login(4) -- login configuration file
|
|
The login.options file is obsolete. All login options are now set in the /etc/default/login file. See login(1) for details. |
|
loginlog(4) -- log of failed login attempts
|
|
/var/adm/loginlog |
|
lvtab(4) -- information about logical volumes
|
|
/etc/lvtab Page 2 lvtab(4) lvtab(4) SEE ALSO lv_to_xlv(1M), PPPPaaaaggggeeee 3333 |
|
master(4) -- master configuration database
|
|
A sample master file for a shared memory module is named shm. The module is an optional loadable software module that can only be specified once. The module prefix is shm, and it has no major number associated with it. In addition, another module named ipc is necessary for the correct operation of this module. *FLAG PREFIX SOFT #DEV DEPENDENCIES ox shm - - ipc shmsys(){nosys} shmexec(){} shmexit(){} shmfork(){} shmslp(){true} shmtext(){} $ #define SHMMAX 131072 #define SHMMIN 1 #define SHMMNI 10... |
|
miser(4) -- configuration files
|
|
The miser configuration file is a list of the queue names and the location of each queue definition file. QUEUE system /usr/local/miser/config.system QUEUE physics /usr/local/miser/config.physics |
|
miser_move(4) -- resource transfer list
|
|
An example resource list transferring a 2 CPUs 2 minutes in the future from queue user to queue user2 is |
|
miser_submit(4) -- resource schedule list
|
|
An example resource schedule list for an application that requires 10 CPUs, 100 megabytes of memory, and 100 minutes of wall clock time: #resource schedule SEGMENT TIME 100m NCPUS 10 MEMORY 100m |
|
mload(4) -- dynamically loadable kernel modules
|
|
1. Loadable modules must not have any dependencies on loadable modules, other than library modules. When a module is loaded, it is linked against the kernel symbol table and any loaded library modules' symbol tables, but it is not linked against other modules' symbol tables. Page 8 mload(4) mload(4) 2. Only character, block and streams device drivers, streams modules and library modules are supported as loadable modules at this time. 3. Old style drivers (devflag set to D_OLD) are not loadable... |
|
motd(4) -- message of the day
|
|
/etc/motd |
|
dmedia/mpeg(4) -- MPEG compression format
|
|
The MPEG compression format is supported by several developer and enduser products. Current support is limited to MPEG-1, Layers I/II audio, and systems streams with one audio track and one video track. |
|
mtab(4) -- mounted filesystem table
|
|
/dev/root / xfs rw,raw=/dev/rroot 0 0 /dev/usr /usr xfs rw,raw=/dev/rusr 0 0 bonnie:/src /net/src nfs ro,hard,bg,intr,dev=1200 0 0 |
|
mtune(4) -- default system tunable parameters
|
|
/var/sysgen/mtune/* default system tunable parameters /var/sysgen/stune local settings for system tunable parameters /var/sysgen/system/* master system configuration files |
|
names_table(4) -- database of registered AppleTalk services
|
|
The names_table file is created and maintained by the Name Binding Protocol daemon (nbpd(1m) (Reg.)contains the names of named AppleTalk services registered by the host users of the Name Binding Protocol services of the K-TALK/Host libraries. It should be removed whenever nbpd(1m) is restarted, for example, with the -S option of nbpd(1m). This file is not meant to be humanly readable, but its contents are decoded by the atservers(1) command.... |
|
nbp_pid(4) -- process ID of nbpd(1m)
|
|
nbp_pid is the file which contains the process ID of the Name Binding Protocol daemon, nbpd(1m). It should be removed whenever nbpd(1m) is restarted, for example, with the -S option of nbpd(1m). The file contains a single integer. |
|
netconfig(4) -- network configuration database
|
|
The network configuration database, /etc/netconfig, is a system file used to store information about networks connected to the system and available for use. The netconfig database and the routines that access it [see getnetconfig(3N)] are part of the UNIX System V Network Selection component. The Network Selection component also includes the environment variable NETPATH a... |
|
netgroup(4) -- list of network groups
|
|
The netgroup data is used only when the nsd(1M) daemon is running. It is supported in any of the protocol libraries included with Irix, but only one protocol may be used. Listing multiple protocols on the netgroups line in nsswitch.conf(4) is not well defined. Page 1 NETGROUP(4) NETGROUP(4) |
|
netrc(4) -- ftp auto-login initialization file
|
|
$HOME/.netrc |
|
networks(4) -- network name database
|
|
/etc/networks If the NFS option is installed and NIS is running, the getnetent(3N) library routines do not access this file. |
|
dmedia/next(4) -- NeXT / Sun .au Audio File Formats
|
|
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... |
|
nostickytmp(4) -- control temporary files
|
|
/etc/config/nostickytmp /etc/config/nocleantmp |
|
notifier.config(4) -- sysmon configuration file
|
|
This file should not be considered user editable. Syntax errors are not handled gracefully. See the release notes for sysmon for other issues. |
|
nsswitch.conf(4) -- name service configuration file
|
|
This file controls the behavior of the name service daemon nsd(1M). It is read by the daemon on startup and is used to build a filesystem maintained by nsd typically mounted on /ns. The paths are of the format /ns/domain/table/protocol/key. Each nsswitch.conf file results in a domain directory under /ns. The /etc/nsswitch.conf file corresponds to /ns/.local, while each file in /var/ns/domains/DOMAINNAME/nsswitch.conf will result in a directory /ns/DOMAINNAME. The file contains a list of maps sup... |
|
opidebug(4) -- definitions for debugging FullPress programs
|
|
This manual page gives definitions for the bitmask of debugging options that programs like opi(1m), fpod(1m) or imagetox(1) require when being run from the UNIX commandline. Most users will be able to turn on debugging for most FullPress programs from the GUI interfaces and can safely ignore this list. While all the FullPress programs will accept any of these bits (and any others not declared here), some of the bits are not applicable to certain programs. Hex bit The debug item it enables 000000... |
|
passwd(4) -- password file
|
|
If the NFS option is installed, the passwd file can also have lines beginning with a `+' (plus sign) which means to incorporate entries from the NIS. There are three styles of + entries in this file: + Means to insert the entire contents of the NIS password file at that point. +name Means to insert the entry (if any) for name from the NIS at that point. Page 2 passwd(4) passwd(4) +@netgroup Means to insert the entries for all members of the network group netgroup at that point. If a + entry has... |
|
ifl/pbm(4) -- portable bitmap file format
|
|
atktopbm(1), brushtopbm(1), cmuwmtopbm(1), g3topbm(1), gemtopbm(1), icontopbm(1), macptopbm(1), mgrtopbm(1), pi3topbm(1), xbmtopbm(1), ybmtopbm(1), pbmto10x(1), pnmtoascii(1), pbmtoatk(1), pbmtobbnbg(1), pbmtocmuwm(1), pbmtoepson(1), pbmtog3(1), pbmtogem(1), pbmtogo(1), pbmtoicon(1), pbmtolj(1), pbmtomacp(1), pbmtomgr(1), pbmtopi3(1), pbmtoplot(1), pbmtoptx(1), pbmtox10bm(1), pbmtoxbm(1), pbmtoybm(1), pbmtozinc(1), pbmlife(1), pbmmake(1), pbmmask(1), pbmreduce(1), pbmtext(1), pbmupc(1), pnm(5), ... |
|
peer_encaps_config(4) -- SNMP version one subagent encapsulator configuration
|
|
This file controls the behavior of the peer_encaps(1M) daemon. It contains information about each SNMP version one subagent that runs on the local system. The peer_encaps daemon registers each subtree with the peer_snmpd master daemon, then for each request converts the possibly version two protocol request into version one packets and forwards it to the encapsulated subagent. Each response is then converted back into the requesting version and sent back. The format of this file is: [AGENT [ON H... |
|
peer_snmpd_config(4) -- SNMP master agent configuration
|
|
This file controls the behavior of the peer_snmpd(1M) daemon. It contains information about manager applications, SNMPv1 community definitions, and SNMPv2 party definitions. For information on the format of v2 party definitions, please rfer to the section SNMPv2 CONFIGURATION. The general format is: MANAGER [ON TRANSPORT ] [SEND [ALL | NO | traplist] TRAPS [TO PORT <#> ] [WITH COMMUNITY ]] COMMUNITY ALLOW op [,op]... |
|
ifl/pgm(4) -- portable graymap file format
|
|
fitstopgm(1), fstopgm(1), hipstopgm(1), lispmtopgm(1), psidtopgm(1), rawtopgm(1), pgmbentley(1), pgmcrater(1), pgmedge(1), pgmenhance(1), pgmhist(1), pgmnorm(1), pgmoil(1), pgmramp(1), pgmtexture(1), pgmtofits(1), pgmtofs(1), pgmtolispm(1), pgmtopbm(1), pnm(5), pbm(5), ppm(5) |
|
pnch(4) -- file format for card images
|
|
|
|
ifl/ppm(4) -- portable pixmap file format
|
|
giftoppm(1), gouldtoppm(1), ilbmtoppm(1), imgtoppm(1), mtvtoppm(1), pcxtoppm(1), pgmtoppm(1), pi1toppm(1), picttoppm(1), pjtoppm(1), qrttoppm(1), rawtoppm(1), rgb3toppm(1), sldtoppm(1), spctoppm(1), sputoppm(1), tgatoppm(1), ximtoppm(1), xpmtoppm(1), yuvtoppm(1), ppmtoacad(1), ppmtogif(1), ppmtoicr(1), ppmtoilbm(1), ppmtopcx(1), ppmtopgm(1), ppmtopi1(1), ppmtopict(1), ppmtopj(1), ppmtopuzz(1), ppmtorgb3(1), ppmtosixel(1), ppmtotga(1), ppmtouil(1), ppmtoxpm(1), ppmtoyuv(1), ppmdither(1), ppmforge... |
|
privilege(4) -- privilege database
|
|
Do not edit /var/sysadm/privilege by hand. The commands addpriv(1M) and rmpriv(1M) are provided for editing the privilege database. |
|
privilegedUsers(4) -- privileged user database.
|
|
/var/sysadm/privilegedUsers should not be edited directly. Use the addpriv(1M) and rmpriv(1M) commands to administer privileged users. |
|
proc(4) -- process (debug) filesystem
|
|
/proc is a filesystem that provides access to the image of each active process in the system. This was historically mounted as /debug. /proc does not consume any disk resources. This interface provides a richer set of functionality and replaces the now obsolete dbg(4), debug(4) interface. The "files" of this filesystem are of the form /proc/nnnnn and /proc/pinfo/nnnnn, where nnnnn is a decimal number corresponding to the process-ID. These files actually consume no disk space, and are only conv... |
|
profile(4) -- setting up an environment at login time
|
|
All users who have the shell, sh(1), as their login command have the commands in these files executed as part of their login sequence. /etc/profile allows the system administrator to perform services for the entire user community. Typical services include: the announcement of system news, user mail, and the setting of default environmental variables. It is not unusual for /etc/profile to execute special actions for the root login or the su(1M) command. The file $HOME/.profile is used for setting... |
|
project(4) -- project membership file
|
|
/etc/project |
|
projid(4) -- project name to project ID mapping file
|
|
/etc/projid |
|
proto(4) -- prototype job file for at
|
|
When a job is submitted to at(1) or batch(1), the job is constructed as a shell script. First, a prologue is constructed, consisting of: o A header whether the job is an at job or a batch job (actually, at jobs submitted to all queues other than queue a, not just to the batch queue b, are listed as batch jobs); the header will be : at job for an at job, and : batch job for a batch job. o A set of Bourne shell commands to make the environment (see environ(5)) for the at job the same as the curren... |
|
protocols(4) -- protocol name database
|
|
/etc/protocols If the NFS option is installed and NIS is running, the getprotoent(3N) library routines do not access this file. |
|
queuedefs(4) -- at/batch/cron queue description file
|
|
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch(1); c is the default queue for jobs run from a crontab file. The name must be a lower case letter. njob The maximum number of jobs that can be... |
|
quotas(4) -- filesystem quota subsystem
|
|
Currently, it is not possible to enable quotas on XFS realtime filesystems. |
|
rcsfile(4) -- format of RCS file
|
|
Author: Walter F. Tichy, Purdue University, West Lafayette, IN, 47907. Revision Number: 5.7; Release Date: 1998/01/12. Copyright c 1982, 1988, 1989 by Walter F. Tichy. Copyright c 1990, 1991, 1992, 1993, 1994, 1995 by Paul Eggert. |
|
resolver(4) -- host-address resolver configuration file (DNS/NIS)
|
|
This file controls the behavior of then resolver(3N) routines in the C library. It is read by these 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. The keyword and value must appear on a single line, and the keyword (for example, nameserver) must start the line. The value follows the keyword, separated by white space. This file is not necessary if there... |
|
rgb(4) -- Silicon Graphics rgb image file format
|
|
IRIS image files are used to store 1,2 and 3 dimensional arrays of pixel values that contain either 1 or 2 bytes per pixel. Pixel values are signed integers that cover the range 0..255 or -32768..32767 (i.e. 1 or 2 bytes). Image files are currently used to store rgb screen dumps, black and white images, color index images, as well as colormaps. The image library provides tools to manipulate these files. To include the image library place the token -limage on the compile line for your program. Al... |
|
rmtab(4) -- remotely mounted file system table
|
|
/etc/rmtab |
|
rpc(4) -- RPC program number data base
|
|
The rpc file contains user readable names that can be used in place of Sun 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/or tab characters. A ``#'' indicates the beginning of a comment; characters up to the end of the line are not interpreted by routines which search the file. Here is an excerpt of the /etc/rpc file on IRIX: # # rpc 1.10 87/04/10 # portmapper 100000 por... |
|
salog(4) -- system administration log
|
|
/var/sysadm/salog System administration log. /var/sysadm/oldsalog Old system administration log. /var/sysadm/salog.conf System administration log configuration file. |
|
satd(4) -- system auditing file format.
|
|
An audit file consists of an Audit File Header followed by a number of AUDIT RECORDS. A new audit record is created for each auditable event. An Audit Record consists of an Audit Record Header Token followed by a number of Audit Tokens. An Audit Token consists of an Audit Token Header followed by token data which is specific to each token. The Audit Token Header consists of an unsigned 16 bit token identifier and an unsigned 16 bit token size field. The contents of the Audit File Header are: ___... |
|
sccsfile(4) -- format of SCCS file
|
|
admin(1), delta(1), get(1), prs(1). PPPPaaaaggggeeee 3333 |
|
scr_dump(4) -- format of curses screen image file.
|
|
The curses(3X) function scr_dump() will copy the contents of the screen into a file. The format of the screen image is as described below. The name of the tty is 20 characters long and the modification time (the mtime of the tty that this is an image of) is of the type time_t. All other numbers and characters are stored as chtype (see ). No newlines are stored between fields. for e... |
|
dmedia/sd2(4) -- Sound Designer II Audio File Format
|
|
The Audio File Library currently supports eight 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, ... |
|
securenets(4) -- NIS map security file
|
|
The /etc/securenets file lists networks and hosts that may participate in the NIS protocol with this host. This file is used by both the NIS server library nisserv(7p). This file contains any number of netmask/address pairs, one per line separated by white space. The netmask controls which bits in an address are contained in the match. It should contain all ones followed by all zeros in binary. A netmask of 255.255.255.255 (all ones in binary) would require an exact match of the address. An exam... |
|
services(4) -- service name database
|
|
It is sometimes useful to be able to determine which processes are using a particular port. This can be accomplished using the fuser(1M) command. For example, in order to see which processes are listening on TCP port 25, the command fuser 25/tcp can be used. Note that fuser only accepts service names in their numeric form; symbolic names such as ``smtp'' cannot be used. |
|
dmedia/sf2(4) -- SoundFont Compatible Audio 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... |
|
shadow(4) -- shadow password file
|
|
/etc/shadow |
|
dmedia/smp(4) -- Sample Vision Audio 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... |
|
snetd.options(4) -- network configuration file
|
|
/etc/config/snetd.options |
|
ssdi(4) -- Standardized Systems Database Interface (SSDI) configuration file
|
|
This file controls the behavior of accesses to standard system databases, such as the passwd and group databases. Normally, each database has its own set of standard access routines. For example, the passwd database routines are defined by getpwent(3C). When such a routine is called, the requested information is iteratively searched through various sources. Usually, all database routines support a standard source which are compiled-in along with them. For example, the standard source for passwd ... |
|
statmon(4) -- statd directories and file structures
|
|
/var/statmon/sm and /var/statmon/sm.bak are directories generated by statd. Each entry in /var/statmon/sm represents the name of a machine to be monitored by statd. Each entry in /var/statmon/sm.bak represents the name of a machine to be notified of statd's recovery. /var/statmon/state is a file generated by statd to record its version number. This version number is incremented each time a crash or recovery takes place.... |
|
strftime(4) -- language-specific strings
|
|
Here are the contents of /usr/lib/locale/C/LC_TIME: Jan Feb ... January February ... Sun Mon ... Sunday Monday Page 1 strftime(4) strftime(4) ... %H:%M:%S %m/%d/%y %a %b %e %H:%M:%S ... |
|
stune(4) -- local settings for system tunable parameters
|
|
/var/sysgen/mtune/* default system parameters /var/sysgen/stune local settings for system tunable parameters |
|
sulog(4) -- log of all su attempts
|
|
/var/adm/sulog log file /etc/default/su defaults file |
|
syms(4) -- MIPS symbol table
|
|
The following information applies to the IRIX 4 COFF symbol table and, for now, the .mdebug section found in 32-bit objects on IRIX 6. In a future IRIX release, the .mdebug section will be replaced. The MIPS symbol table departs from the standard COFF symbol table. The symbol table consists of many tables unbundling information usually found in the one COFF symbol table. The symbol table should be viewed as a hand-crafted, network-style database designed for space and access efficiency. The foll... |
|
dmedia/synthpreset(4) -- MIDI synthesizer preset file
|
|
The current midi synthesizer identifies preset files via a string which must be used as the first line of the file. Following this is the word PRESET in all capital letters, on its own line: #Synth Preset v1.0 |
|
system(4) -- system configuration information directory
|
|
/var/sysgen/system/*.sm /usr/include/sys/edt.h |
|
sys_id(4) -- system identification (hostname) file
|
|
/etc/sys_id |
|
term(4) -- format of compiled term file
|
|
Compiled terminfo(4) descriptions are placed under the directory /usr/share/lib/terminfo. In order to avoid a linear search of a huge UNIX system directory, a two-level scheme is used: /usr/share/lib/terminfo/c/name where name is the name of the terminal, and c is the first character of name. Thus, att4425 can... |
|
terminfo(4) -- terminal capability data base
|
|
terminfo is a database produced by tic that describes the capabilities of devices such as terminals and printers. Devices are described in terminfo source files by specifying a set of capabilities, by quantifying certain aspects of the device, and by specifying character sequences that effect particular results. This database is often used by screen oriented applications such as vi and curses programs, as well as by... |
|
timezone(4) -- set default system time zone
|
|
This file sets the time zone environmental variable TZ. This file is read by init(1) after system boot up and all subsequent processes inherit TZ in their environment. Other variables than TZ may also be set in this file, for programs that are run from init. Some programs started by init reset all or part their environment, and therefore these variables may not be seen by all programs. The form of the variables is TZ =value Lines that are too long are ignored; in practice... |
|
ts.config(4) -- tape support configuration file
|
|
The tape support configuration file is ts.config. This file defines the location of the personality-daemon binaries and the options available for executing the tsdaemon(1M) command. The tape support configuration file consists of statements and comments (optional). A comment begins with the # symbol and continues to the end of line. A statement consists of a name followed by a list of keyword parameters. The following statements are supported: o... |
|
ttytype(4) -- data base of terminal types by port
|
|
iris-ansi console vt100 ttyd1 ?h19 ttyd2 ?h19 ttyd3 ?v50am ttyd4 ?v50am ttyd5 ?v50am ttyd6 ?v50am ttyd7 ?v50am ttyd8 ?v50am ttyd9 ?v50am ttyd10 ?v50am ttyd11 ?v50am ttyd12 |
|
unistd(4) -- file header for symbolic constants
|
|
The header file lists the symbolic constants and structures not already defined or declared in some other header file. /* Symbolic constants for the "access" routine: */ #define R_OK 4 /*Test for Read permission */ #define W_OK 2 /*Test for Write permission */ #define X_OK 1 /*Test for eXecute permission */ #define F_OK 0 /*Test for existence of File */ #define F_ULOCK 0/*Unlock a previously locked region */ #define F_LOCK 1/*Lock a region for exclusive use */ #define F_TLOCK 2/*Tes... |
|
uns(4) -- the Unified Name Service Architecture
|
|
|
|
updaters(4) -- configuration file for NIS updating
|
|
The file /var/yp/updaters is a makefile (see make(1)) which is used for updating NIS databases. Each entry in the file is a make target for a particular NIS database. For example, if there is a NIS database named passwd.byname that can be updated, there should be a make target named passwd.byname in the updaters file with the command to update the file. The information necessary to make the update is passed to the update command through standard input. The information passed is described below (... |
|
utmp(4) -- utmp and wtmp entry formats
|
|
These files, which hold user and accounting information for such commands as who, last, write, and login, contain entries with the following structure, defined in utmp.h: #define UTMP_FILE "/var/adm/utmp" #define WTMP_FILE "/var/adm/wtmp" #d... |
|
utmpx(4) -- utmp and wtmp extended-format entries
|
|
utmpx and wtmpx files are extended versions of utmp and wtmp, resp., containing records of type struct utmpx. The utmpx struct is a superset of the utmp struct, containing both additional fields and larger array allocation for several existing fields. utmpx's most significant addition is the ut_host field, which identifies the host from which the ent... |
|
uuencode(4) -- format of an encoded uuencode file
|
|
uuencode(1C), uudecode(1C), uucp(1C), mail(1) PPPPaaaaggggeeee 1111 |
|
visuallogin(4) -- select and control console login program
|
|
/etc/config/visuallogin /etc/config/noiconlogin |
|
dmedia/voc(4) -- Creative Voice Audio 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/wave(4) -- Microsoft RIFF WAVE 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... |
|
xfs(4) -- layout of the XFS filesystem
|
|
attr(1), grio(1M), mkfs(1M), mkfs_xfs(1M), xfs_bmap(1M), xfs_check(1M), xfs_copy(1M), xfs_estimate(1M), xfs_growfs(1M), xfs_logprint(1M), xfs_repair(1M), xfsdump(1M), xfsrestore(1M), fcntl(2), syssgi(2), uuid(3C), filesystems(4), lv(7M), xlv(7M). Page 2 filesystems(4) filesystems(4) |
|
X11/ximconf(4) -- Configuration file of Input Manager of the X Window System Version 11 (xwnmo(1X))
|
|
ximconf contains the information regarding the configurations of xwnmo, such as, environments of each supported languages(the relation between internal locale and external locale, CSWIDTH(code set width), whether use conversion server or not and etc.), default locale and locale for world environment. Lines that start with a semicolon (;) are comments. Coding format: {ext_locale}[|{ext_locale}|...] {lang} {internal_locale} {cswidth} {using_server} {code_trans} or setdefaultlocale {def_locale} or ... |
|
X11/ximrc(4) -- Environment setting file of Input Manager of the X Window System Version 11 (xwnmo(1X))
|
|
The ximrc file sets up the environment for the xwnmo. Individual settings can be specified for each user. Duplicate entries will be overwritten. Lines that start with a semicolon (;) are comments. Xwnmo will search this file as follows: 1. Resource "ximrcName" 2. $HOME/.ximrc 3. /usr/lib/wnn/ximrc (Default) The following settings are specified in this file. Any setting which is not specified will use the default value. setuumrc Specifie... |
|
X11/xjutil(4) -- Dictionary Utility Manager
|
|
The xjutil is a dictionary utility manager operates dictionaries of Wnn. It is executed by xwnmo automatically. |
|
xlate(4) -- the address translation object file section of an ELF object
|
|
An address translation section is created by commands such as pixie(1), and cord(1) to allow other tools such as dbx(1) and dis(1) to accurately display information about the program text. There can be a maximum of two address translation sections (one of each section type (see below)) in a given a.out or DSO. Translation information is held in ELF sections with sh_type SHT_MIPS_XLATE (section name .MIPS.Xlate), SHT_MIPS_XLATE_DEBUG (not currently generated by cord or pixie), or SHT_MIPS_XLATE_O... |
|
ypfiles(4) -- the NIS database and directory structure
|
|
makemdbm(1M), ypinit(1M), ypmake(1M), ypxfr(1M), yppush(1M), yppoll(1M), nsd(1M), rpcinfo(1M), mdbm(3B), nis(7P) PPPPaaaaggggeeee 2222 |
|
ypservers(4) -- NIS bindings file
|
|
The file /var/yp/binding/DOMAINNAME/ypservers contains a static list of available NIS servers for the domain DOMAINNAME. If this file exists, then only the servers listed in it are eligible to act as NIS servers for this client. The file contains a whitespace separated list of host names or IP addresses. If a name is given then an entry for this host must exist in the local hosts file /etc/hosts. An example file would be: 128.1.2.1 bigserver 192.0.1.1 150.166.2.3 This file lists four hosts which... |
