HP-UX Reference Section 4: File Formats HP-UX 11i Version 2 Volume 8 of 9 Manufacturing Part Number : B2355-90786 Printed In USA E0803 Printed in USA © Copyright 1983-2003 Hewlett-Packard Development Company LP.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Copyright 1980, 1984, 1986 Novell, Inc. Copyright 1985, 1986, 1988 Massachusetts Institute of Technology Copyright 1986-2000 Sun Microsystems, Inc. Copyright 1988 Carnegie Mellon University Copyright 1989-1991 The University of Maryland Copyright 1989-1993 The Open Software Foundation, Inc. Copyright 1990 Motorola, Inc. Copyright 1990-1992 Cornell University Copyright 1991-2003 Mentat, Inc. Copyright 1996 Morning Star Technologies, Inc. Copyright 1996 Progressive Systems, Inc.
Revision History This document’s printing date and part number indicate its edition. The printing date changes when a new edition is printed. (Minor corrections and updates which are incorporated at reprint do not cause the date to change.) New editions of this manual incorporate all material updated since the previous edition. Part Number Date, Release, Format, Distribution B2355-60103 August 2003. HP-UX release 11i version 2, one volume HTML, docs.hp.com and Instant Information.
manpage itself. From the HP-UX command line, you can enter “man audit” or “man 5 audit” to view the manpage. See man (1). Book Title The title of a book. On the web and on the Instant Information CD, it may be a hot link to the book itself. KeyCap The name of a keyboard key. Note that Return and Enter both refer to the same key. Emphasis Text that is emphasized. Emphasis Text that is strongly emphasized. ENVIRONVAR The name of an environment variable.
vi
Preface HP-UX is the Hewlett-Packard Company’s implementation of an operating system that is compatible with various industry standards. It is based on the UNIX System V Release 4 operating system and includes important features from the Fourth Berkeley Software Distribution. The nine volumes of this manual contain the system reference documentation, made up of individual entries called manpages, named for the man command that displays them on the system.
viii
Volume Eight Table of Contents Section 4
Volume Eight Table of Contents Section 4
Table of Contents Volume Eight Section 4: File Formats Entry Name(Section): name Description intro(4): intro ....................................................................................................... introduction to file formats .rhosts: security files authorizing access by remote hosts and users on local host ........... see hosts.equiv(4) password file format ....................................................................................................... see passwd(4)
Table of Contents Volume Eight Entry Name(Section): name Description ioconfig(4): ioconfig ..................................................................................................... ioconfig entry format issue(4): issue .............................................................................................................. issue identification file krb5.conf(4): krb5.conf .......................................................................................
Table of Contents Volume Eight Entry Name(Section): name Description tcpd.conf(4) ................................................................................................................ configuration file for tcpd term: terminal capabilities ............................................................................................................. see term_c(4) term(4): term ........................................................................................................
Notes xii Hewlett-Packard Company HP-UX 11i Version 2: August 2003
Section 4 File Formats
Section 4 File Formats
intro(4) intro(4) NAME intro - introduction to file formats DESCRIPTION This section outlines the formats of various files. The C struct declarations for the file formats are given where applicable. Usually, these structures can be found in directories /usr/include or /usr/include/sys. SEE ALSO hier(5), introduction(9). A A Web access to HP-UX documentation at http://docs.hp.com.
a.out(4) a.out(4) NAME a.out - assembler and link editor output SYNOPSIS #include (for ELF files) #include (for SOM files) A aA DESCRIPTION ELF a.out The file name a.out is the default output file name from the link editor, ld(1). The link editor will make an a.out executable if there were no errors in linking. The output file of the assembler, as (1), also follows the format of the a.out file although its default file name is different.
a.out(4) a.out(4) the sum of the next maximal page boundary past the end of text plus the remainder of the last text address divided by the maximal page size. If the last text address is a multiple of the maximal page size, no duplication is necessary. The stack is automatically extended as required. The data segment is extended as requested by the brk(2) system call. SOM a.out (PA-RISC Only) The file name a.
a.out(4) a.out(4) In a relocatable file, initialized code and data often contain references to locations elsewhere in the file, and to unresolved symbols defined in other files. These references are patched at link time using the relocation information. Each entry in the relocation information (a "fixup") specifies a location within the initialized data for a subspace, and an expression that defines the actual value that should be placed at that location, relative to one or two symbols.
a.out(4) a.out(4) struct sys_clock { unsigned int secs; unsigned int nanosecs; }; Auxiliary Headers The auxiliary headers are contained in a single contiguous area in the file, and are located by a pointer in the file header. Auxiliary headers are used for two purposes: to attach users’ version and copyright strings to an object file, and to contain the information needed to load an executable program. In an executable program, the HP-UX auxiliary header must precede all other auxiliary headers.
a.out(4) a.
a.out(4) a.out(4) int unsigned int fixup_request_index; /* index to first fixup */ fixup_request_quantity; /* # of fixup requests */ }; Symbol Table The symbol table consists of a sequence of entries described by the structure shown below, from . Strings for symbol and qualifier names are contained in the symbol strings table, whose structure is identical with the space strings table.
a.out(4) A aA a.out(4) If a relocatable file is compiled with parameter type checking, extension records follow symbols that define and reference procedure entry points and global variables. The first extension record, the symbol extension record, defines the type of the return value or global variable, and (if a procedure or function) the number of parameters and the types of the first three parameters.
a.out(4) a.out(4) struct/array 17 For procedure entry points, the parameter relocation bits define the locations of the formal parameters and the return value. Normally, the first four words of the parameter list are passed in general registers (r26-r23) instead of on the stack, and the return value is returned in r29. Floating-point parameters in this range are passed instead in floating-point registers (fr4-fr7) and a floating-point value is returned in fr4.
a.out(4) #define #define #define #define #define #define #define a.
a.out(4) a.out(4) R_DP_RELATIVE Copy one instruction word with relocation. The word is assumed to be a dprelative load or store instruction (for example, ADDIL, LDW, STW). The target symbol is identified by symbol S. The linker forms the difference between the value of the symbol S and the value of the symbol $global$. By convention, the value of $global$ is always contained in register 27. Instructions may have a small constant in the displacement field of the instruction.
a.out(4) A aA a.out(4) R_RSEL Use an R-class field selector for the next fixup request instead of the default appropriate for the instruction. Depending on the current rounding mode, R´, RS´, RD´, or RR´ may be used. R_N_MODE Select round-down mode (L´/R´). This is the default mode at the beginning of each subspace. This setting remains in effect until explicitly changed or until the end of the subspace. R_S_MODE Select round-to-nearest-page mode (LS´/RS´).
a.out(4) a.out(4) side effect of this fixup request, the referenced fixup is moved to the front of the queue. R_N0SEL Indicates that the following fixup is applied to the first of a three-instruction sequence to access data, generated by the compilers to enable the importing of shared library data. R_N1SEL Uses a (N´) field selector for the next fixup request. This indicates that zero bits are to be used for the displacement on the instruction.
a.out(4) a.
a.out(4) R_LTP_OVERRIDE R_COMMENT R_TP_OVERRIDE R_RESERVED a.out(4) 220 221 222 224-255 1 6 1 none OP = B1; V = B2 to B6 none reserved Parameter relocation bits are encoded in the fixup requests in two ways, noted as rbits1 and rbits2 in the above table. The first encoding recognizes that the most common procedure calls have only general register arguments with no holes in the parameter list.
acct(4) acct(4) NAME acct - per-process accounting file format SYNOPSIS #include DESCRIPTION Files produced as a result of calling acct() (see acct (2)) have records in the form defined by
acct(4) acct(4) executed by the process. Kernel internal structures may change from release to release without warning. Applications directly relying on these structures are not supported. Accounting files are currently written in 32-bit format. Thus, 64-bit applications which read the files need to make special provisions. In particular, the acct.h header declares the ac_btime field as int32_t rather than a time_t in 64-bit compilations.
ar(4) ar(4) NAME ar - common archive file format SYNOPSIS #include DESCRIPTION The ar command is used to concatenate several files into an archive file (see ar (1)). Archives are used mainly as libraries to be searched by the link editor (see ld(1)). A aA Each archive begins with the archive magic string. #define #define ARMAG SARMAG "!\n" 8 /* magic string */ /* length of magic string */ Following the archive magic string are the archive file members.
ar(4) ar(4) contains /27 in the ar_name field. The long name string table would have the following format: 0 10 20 30 40 50 +0 t y a a g o +1 +2 | h | i | l | o | m | e | n | o | f | i | / | \n | | | | | | +3 s n . t l | | | | | +4 i g o h e | | | | | +5 s f / e n +6 +7 | a | v | i | l | \n | y | r | l | a | m | | | | | +8 e e e o e | | | | | +9 r n t n . | | | | | A SEE ALSO System Tools: ar (1) ld(1) Miscellaneous: a.
audeventstab(4) audeventstab(4) NAME audeventstab - define and describe audit system events DESCRIPTION The /usr/audit/audeventstab file lists audit event numbers, corresponding mnemonic names, and brief explanations of each event. Blank lines and comments (beginning with a # character) are allowed. Each non-comment, non-blank line in this file contains three parts: A aA event Audit event number in decimal: a single field separated by whitespace.
audit(4) audit(4) NAME audit - file format and other information for auditing SYNOPSIS #include DESCRIPTION Audit records are generated when users make security-relevant system calls, as well as by self-auditing processes that call audwrite() (see audwrite (2)). Access to the auditing system is restricted to superuser. Each audit record consists of an audit record header and a record body. The record header is comprised of time, process ID, error, event type, and record body length.
authcap(4) authcap(4) NAME authcap - security databases for trusted systems SYNOPSIS /tcb/files/auth/* /tcb/files/auth/system/* A aA DESCRIPTION All security-relevant databases are stored in an ASCII format in the file system. This format is converted to binary structures by support routines described in Section 3 manual entries. This manual entry describes the format of these databases, and describes the philosophy of conversion into data structures.
authcap(4) authcap(4) where num is a decimal or (0-preceded) octal number. Boolean capabilities have the format: id or id@ where the first form signals the presence of the capability and the second form signals the absence of the capability. String capabilities have the format: id=string where string is 0 or more characters. The \ and : characters are escaped as \ \ and \: respectively. File Locking All databases use a lock file, the existence of which means that the file is currently being rewritten.
bootconf(4) bootconf(4) NAME bootconf - boot device configuration table DESCRIPTION This file, /stand/bootfonf, contains the address and disk layout type of the system’s boot devices or lif volumes. It is used by the Software Distributor and HP-UX kernel control scripts (fileset OSCore.KERN-RUN) to determine how and where to update the initial boot loader. Normally the kernel’s checkinstall script queries the system’s hardware and creates the file.
bootconf(4) # # # # l l l bootconf(4) Boot Device configuration file This file contains information regarding the location of the boot LIF. It is used by the KERN-RUN fileset to update the boot kernel. /dev/dsk/c1d0s2 /dev/dsk/c4d0s2 /dev/dsk/c5d0s2 The boot area is on a hard partitioned disk: # # # # p Boot Device configuration file This File contains information regarding the location of the boot LIF. It is used by the KERN-RUN fileset to update the boot kernel.
cdnode(4) cdnode(4) NAME cdnode - format of a CDFS cdnode SYNOPSIS #include #include DESCRIPTION This entry describes the cdnode structure and related concepts for the CDFS file system. A cA The CDFS file system does not have the concept of a separate entity called an inode. The information normally found in an HFS inode is kept in a cdnode data structure.
cdrom(4) cdrom(4) NAME cdrom - CD-ROM background information DESCRIPTION This manual entry provides general information on existing CD-ROM standards, terminology, data layout, and levels of support. More detailed information is available in the standard documents listed in SEE ALSO. Not all topics discussed here are supported in the current HP-UX release. Refer to the DEPENDENCIES section for details about the contents of the current release.
cdrom(4) cdrom(4) and File Data (described below) to minimize seek times. The Directory and File Data contains data for all directory hierarchies on the CD-ROM and, as described above, can be made noncontiguous by the occasional inclusion of a path table. Volumes and Directory Hierarchies A volume is a single physical CD-ROM. A directory hierarchy is a hierarchical file system written on a volume.
cdrom(4) cdrom(4) numerical values are recorded most-significant-byte-first. One of each type of path table is required by both standards. The ISO standard allows for one additional optional copy of each type of path table, while the HSG standard allows for up to three additional optional copies of each type. Additional copies of path tables are useful for redundancy or seek time minimization.
cdrom(4) cdrom(4) Level 1 The system is permitted to ignore supplementary volume descriptors, their associated path tables, and all directory and file data associated with them. Level 2 No restrictions apply. In all cases, receiving systems must fulfill the receiving system requirements specified in section 10 of the ISO standard (no equivalent section exists for HSG). Interchange levels provide a way to specify the data structure and complexity that exists on a CDROM.
charmap(4) charmap(4) NAME charmap - symbolic translation file for localedef scripts SYNOPSIS localedef -f charmap locale_name DESCRIPTION Invoking the localedef command with the -f option causes symbolic names in the locale description file to be translated into the encodings given in the charmap file (see localedef (1M)). As a recommendation, a locale description file should be written completely with symbolic names.
charmap(4) charmap(4) The encoding is a character constant in one of three forms: decimal An escape character followed by the letter d, followed by one to three decimal digits. octal An escape character followed by one to three octal digits. hexadecimal An escape character followed by an x, followed by two hexadecimal digits. Multibyte characters are represented by the concatenation of character constants. All constants used in the encoding of a multibyte character must be of the same form.
core(4) core(4) NAME core - format of core image file DESCRIPTION The HP-UX system writes out a file containing a core image of a terminated process when certain signals are received (see signal (5) for the list of reasons). The most common causes are memory violations, illegal instructions, floating point exceptions, bus errors, and user-generated quit signals. The core image file is called core and is written in the process’s working directory (provided it is allowed by normal access controls).
cpio(4) cpio(4) NAME cpio - format of cpio archive DESCRIPTION The header structure, when the -c option of cpio is not used (see cpio (1)), is: struct { short ushort A cA short char } Hdr; c_magic, c_dev; c_ino, c_mode, c_uid, c_gid; c_nlink, c_rdev, c_mtime[2], c_namesize, c_filesize[2]; c_name[c_namesize rounded to word]; When the cpio -c option is used, the header information is described by: sscanf(Chdr,"%6ho%6ho%6ho%6ho%6ho%6ho%6ho%6ho%11lo%6ho%11lo", &Hdr.c_magic,&Hdr.c_dev,&Hdr.c_ino,&Hdr.
default(4) default(4) NAME default - system default database file for a trusted system SYNOPSIS /tcb/files/auth/system/default DESCRIPTION The system default database is unique in that it defines system-wide global parameters for a trusted system. It is designed to provide values for users and devices on a global scale rather than requiring an administrator to replicate values in user or device databases when they are all the same.
default(4) default(4) The system default database also defines numerous protected password database default values. Fields that begin with u_ correspond to protected password fields. Similarly, fields starting with the t_ prefix are terminal control database fields. These field types are used to supply system-wide default values if a user or device specific value is not supplied by the corresponding database.
devassign(4) devassign(4) NAME devassign - device assignment database file for a trusted system SYNOPSIS /tcb/files/devassign DESCRIPTION The system supports a single device assignment database that contains entries for local login terminals. The format of the terminal control database file is identical to other trusted system authentication database files. For more information on the file format, see authcap (4). The file consists of keyword field identifiers and values for those fields.
dialups(4) dialups(4) NAME dialups, d_passwd - dialup security control DESCRIPTION dialups and d_passwd are used to control the dialup security feature of login (see login (1)). If /etc/dialups is present, the first word on each line is compared with the name of the line upon which the login is being performed (including the /dev/, as returned by ttyname() (see ttyname (3C)). If the login is occurring on a line found in dialups, dialup security is invoked. Anything after a space or tab is ignored.
dir(4) dir(4) NAME dir - format of directories on short-name HFS file systems SYNOPSIS #include #include Remarks This entry describes the System V-compatible directory format for the HFS file system. It is provided strictly for backward compatibility and compatibility with applications expecting a System V file system environment. It is not compatible with the similar but more general HFS directory format in
disktab(4) disktab(4) NAME disktab - disk description file SYNOPSIS #include DESCRIPTION disktab is a simple database that describes disk geometries. Entries in disktab consist of a number of colon-separated fields. The first entry for each disk gives the names by which the disk is known, separated by vertical bar (|) characters. This file is provided for backward compatibility with previous HP-UX releases only. discouraged.
dlpi(4) dlpi(4) NAME dlpi.h - data link provider interface standard header file SYNOPSIS /usr/include/sys/dlpi.h DESCRIPTION is the standard header file containing DLPI requests as prescribed by the DLPI 2.0 standard. It contains the definitions for the primitives, acknowledgements and associated structures. The header file must be included by all DLS users (user-space and kernel-space) who intend to interact with LAN drivers through DLPI.
dlpi_drv(4) dlpi_drv(4) NAME dlpi_drv.h - definitions of interfaces for device drivers to interact with DLPI SYNOPSIS /usr/include/sio/dlpi_drv.h DESCRIPTION The header file contains definitions of structures and function prototypes that are required by networking device drivers to interact with DLPI (data link provider interface). The header file contains interfaces that could be used by tightly coupled and loosely coupled drivers.
dlpi_ext(4) dlpi_ext(4) NAME dlpi_ext.h - HP-specific extensions for DLPI SYNOPSIS /usr/include/sys/dlpi_ext.h DESCRIPTION is the header file for HP-specific extensions to data link provider interface, DLPI 2.0 standard. The header file contains definitions for primitives, acknowledgements, ioctls and associated structures to satisfy needs of DLS users over and beyond what is provided by DLPI 2.0 standard.
dosif(4) dosif(4) NAME DOSIF - DOS Interchange Format description DESCRIPTION The commands doschmod, doscp, dosdf, dosls, dosll, dosmkdir, dosrm, and dosrmdir are targeted for removal from HP-UX. Use the dos2ux and ux2dos commands to convert files between HP-UX and DOS file formats; see dos2ux (1). DOSIF (DOS Interchange Format) is the name given to the media format used by the DOS operating system. This format is based upon that used in IBM PC and PC AT and HP Vectra systems.
dp(4) dp(4) NAME dp - dedicated ports file used by DDFA software and Telnet port identification feature DESCRIPTION The dp file has two uses: Datacommunications and Terminal Controller Device File Access The dp file is used by the Datacommunications and Terminal Controller Device File Access (DDFA) software to allow terminal server ports to be programmatically accessed from HP-UX applications in the same way as devices connected directly to the HP-UX system.
dp(4) dp(4) If the dtc_name field explicitly defines the node name or the IP address of the terminal server port, the value in the board /port field must be xx/xx (use X or x). If the field is of the form xx/n where n is a decimal number, n is assumed to be the TCP port service address and it is used when the connection is established. A pseudonym This field is the absolute path of the device file known to the system and the end-user application.
dp(4) dp(4) /usr/examples/ddfa/pcf SEE ALSO dpp(1M), ocd(1M), ocdebug(1M), syslog(3C), pcf(4), ddfa(7).
efi(4) efi(4) NAME efi - Extensible Firmware Interface description DESCRIPTION The EFI (Extensible Firmware Interface) is an interface between HP-UX and the Itanium(R)-based platform firmware. The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI encompasses the use of FAT-32 for a system partition, and FAT-12 or FAT-16 for removable media. The system partition is required on a bootable disk for the Itanium-based platform.
exports(4) exports(4) NAME exports, xtab - directories to export to NFS clients SYNOPSIS /etc/exports /etc/xtab DESCRIPTION File /etc/exports describes the directories that can be exported to NFS clients. The system administrator creates it using a text editor. mountd processes it each time a mount request is received (see mountd (1M)). /etc/exports is read automatically by the exportfs command (see exportfs (1M)).
exports(4) exports(4) hostname; this HP-only feature will be obsoleted in a later release of HP-UX. netgroup A netgroup contains a number of hostnames. With a server configured for DNS naming in the nsswitch "hosts" entry, any hostname in a netgroup must be represented as a fully qualified DNS name. DNS suffix To use domain membership the server must use DNS to resolve hostnames to IP addresses; that is, the "hosts" entry in the /etc/nsswitch.
exports(4) exports(4) /usr/bin -ro # export read-only to everyone /usr/stuff -access=bear,anon=-2,ro # several options on one line /usr/subnet -access=@mysubnet #use mysubent in /etc/networks /usr/subnet1 -access=@192.5 #clients must be in the 192.5.0.0 subnet /usr/domain -access=.myd.myc.com #clients must be in .myd.myc.com /usr/restrict -access=-host1.myd.myc.com:sales # disallow -host1 in the sales netgroup.
fspec(4) fspec(4) NAME fspec - format specification in text files DESCRIPTION It is sometimes convenient to maintain text files on the HP-UX system with non-standard tabs, (meaning tabs that are not set at every eighth column). Generally, such files must be converted to a standard format − frequently by replacing all tabs with the appropriate number of spaces − before they can be processed by HP-UX system commands.
fstab(4) fstab(4) NAME fstab - static information about the file systems SYNOPSIS #include DESCRIPTION fstab is an ASCII file that resides in directory /etc. Programs read it, but do not write to or from it. System administrators are responsible for creating and maintaining this file properly. /etc/fstab contains a list of mountable file-system entries. Each file-system entry appears on a separate line, and consists of fields separated by one or more blanks or tabs.
fstab(4) fstab(4) backup frequency Reserved for possible use by future backup utilities. pass number Used by the fsck command to determine the order in which file system checks are done. The root file system should be specified with a pass number of 1, to be checked first, and other file systems should have larger numbers. (A file system with a pass number of zero is ignored by the fsck command.
fstab(4) fstab(4) SEE ALSO fsck(1M), mount(1M), swapon(1M), crashconf(1M), getfsent(3X), getmntent(3X), mnttab(4).
fs_vxfs(4) fs_vxfs(4) NAME fs_vxfs - format of a VxFS file system volume SYNOPSIS #include #include #include DESCRIPTION The VxFS super-block always begins at byte offset 8192 from the start of the file system. The super-block location is fixed so that various system utilities know where to locate it. Super-block fields contain the following fundamental sizes and offsets: A fA fs_bsize The block size of the file system.
fs_vxfs(4) fs_vxfs(4) fs_boffmask A mask value such that (byte_offset & fs_boffmask) yields the offset from the start of the nearest smaller block boundary. fs_bshift The log base 2 of fs_bsize . Used to convert a byte offset into a block offset. fs_bstart The offset, in blocks, of the first data block from the start of an allocation unit. An allocation unit header may contain padding to align the first data block to a specific boundary. fs_checksum A checksum of the above fields.
fs_vxfs(4) fs_vxfs(4) fsadm_vxfs (1M) for a description of file system expansion. VX_UPGRADING Set when a file system upgrade is in progress. If an fsck detects this flag, it performs an upgrade recovery. fs_fname File system name (6 characters). fs_fpack File system pack label (6 characters). fs_free The number of free data blocks. fs_logversion The version number of the log format.
ftpaccess(4) ftpaccess(4) NAME ftpaccess - ftpd configuration file SYNOPSIS /etc/ftpd/ftpaccess DESCRIPTION The /etc/ftpd/ftpaccess file is used to configure the operation of ftpd (see ftpd (1M)). Access Capabilities autogroup groupname class [ class ... ] If an anonymous user is a member of any of class , the ftp server will perform a setgid() to groupname . This allows access to group-and-owner-read-only files and directories to a particular class of anonymous users.
ftpaccess(4) ftpaccess(4) The group name may be specified by either name or numeric ID. To use a numeric group ID, place a % before the number. Ranges may be given. Use an asterisk (*) to mean all groups. guestuser works like guestgroup, except it uses the user name (or numeric ID). realuser and realgroup have the same syntax, but reverse the effect of guestuser and guestgroup. They allow real user access when the remote user would otherwise be determined a guest.
ftpaccess(4) ftpaccess(4) file-limit [ raw ] { in|out|total } count [ class ] Limit the number (count ) of data files that a user in the given class may transfer. The limit may be placed on files in, out or total. If class is not specified, the limit is the default for those classes which do not have a limit specified. The optional raw parameter applies the limit to the total traffic rather than just data files.
ftpaccess(4) ftpaccess(4) private { yes|no } After a user logs in, the SITE GROUP and SITE GPASS ftpd commands may be used to specify an enhanced access group and associated password. If the group name and password are valid, the user becomes (via setgid()) a member of the group specified in the group access file, /etc/ftpd/ftpgroups. The format of the group access file is: access_group_name :encrypted_password :real_group_name where access_group_name is an arbitrary (alphanumeric and punctuation) string.
ftpaccess(4) ftpaccess(4) cookies are available: %T local time (form Thu Nov 15 17:12:42 1990) %C current working directory %E the maintainer’s email address as defined in ftpaccess %R remote host name %L local host name %u username as determined via RFC931 authentication %U username given at login time %M maximum allowed number of users in this class %N current number of users in this class %B absolute limit on disk blocks allocated %b preferred limit on disk blocks %Q current blo
ftpaccess(4) ftpaccess(4) log transfers typelist directions Enables logging of file transfers for either real or anonymous FTP users. Logging of transfers TO the server (incoming) can be enabled separately from transfers FROM the server (outbound). typelist is a comma-separated list of any of the keywords anonymous, guest and real. If the real keyword is included, logging will be done for users using FTP to access real accounts.
ftpaccess(4) ftpaccess(4) /etc/ftpd/ftpaccess file. If the user were to give the command: cd foo The directory will be searched for in the following order: ./foo an alias called foo /pub/packages/foo /.aliases/foo The cd path is only available with the cd command. If you have a large number of aliases, you might want to set up an aliases directory with links to all of the areas that you wish to make available to users. compress { yes|no } classglob [ classglob ...
ftpaccess(4) ftpaccess(4) not be matched. virtual address { hostname|email } string Sets string to either the hostname shown in the greeting message and STAT command, or to the email address used in message files and on the HELP command. virtual address allow username [ username ... ] virtual address deny username [ username ... ] Normally, real and guest users are not allowed to log in on the virtual server unless they are guests and chroot’d to the virtual root.
ftpaccess(4) ftpaccess(4) cidr is shorthand for an IP address in dotted-quad notation followed by a slash and the number of left-most bits which represent the network address (as opposed to the machine address). For example, if you are using the reserved class-A network 10, instead of a netmask of 255.0.0.0, use a cidr of /8 as in 10.0.0.0/8 to represent your network. Note: This option is not supported on IPv6 enabled systems . pasv-allow class [ addrglob ... ] port-allow class [ addrglob ...
ftpaccess(4) ftpaccess(4) Allows or disallows the ability to perform the specified function. By default, all users are allowed. typelist is a comma-separated list of any of the keywords anonymous, guest, real and class=. When class= appears, it must be followed by a classname. If any class= appears, the typelist restriction applies only to users in that class. passwd-check { none|trivial|rfc822 } [ enforce|warn ] Define the level and enforcement of password checking done by the server for anonymous ftp.
ftpaccess(4) ftpaccess(4) upload only applies to users who have a home directory (the argument to the chroot()) of rootdir . root-dir may be specified as "*" to match any home directory. The owner and/or group may each be specified as "*", in which case any uploaded files or directories will be created with the ownership of the directory in which they are created. The optional first parameter selects whether root-dir names are interpreted as absolute or relative to the current chroot’d environment.
ftpaccess(4) ftpaccess(4) allow-gid ftp allow-uid ftp denies ftp access to all privileged or special users and groups on a Linux box except the anonymous ftp user/group. In many cases, this can eliminate the need for the /etc/ftpd/ftpusers file. Support for that file still exists so it may be used when changing /etc/ftpd/ftpaccess is not desired. Throughout the ftpaccess file, at any place that a single UID or GID is allowed, either names or numbers may be used. To use numbers, put a % before it.
ftpaccess(4) ftpaccess(4) dns resolveroptions +aaonly -dnsrch turns on the aaonly option (only accept authoritative answers) and turns off the dnsrch option (search the domain path). WARNINGS IPv6 is supported on HP-UX 11i Version 1.0, with the optional IPv6 software installed. Currently, IPv6 is not supported on systems running HP-UX 11i Version 1.6. FILES /etc/ftpd/ftpaccess AUTHOR ftpaccess was developed by the Washington University, St. Louis, Missouri. SEE ALSO ftpshut(1), groups(1), ftpgroups(4).
ftpconversions(4) ftpconversions(4) NAME ftpconversions - ftpd conversions database SYNOPSIS /etc/ftpd/ftpconversions DESCRIPTION The conversions known by ftpd and their attributes are stored in an ASCII file that is structured as below. Each line in the file provides a description for a single conversion. Fields are separated by colons (:).
ftpgroups(4) ftpgroups(4) NAME ftpgroups - group password file for use with the SITE GROUP and SITE GPASS commands. SYNOPSIS /etc/ftpd/ftpgroups DESCRIPTION The ftpgroups file is the group password file for use with the SITE GROUP and SITE GPASS commands. To enable the use of this file, the entry private /etc/ftpd/ftpaccess. yes must be made in the configuration file This file contains an alphanumeric string, encrypted password, and the actual group name from the /etc/group file.
ftphosts(4) ftphosts(4) NAME ftphosts - ftpd individual user host access file SYNOPSIS /etc/ftpd/ftphosts DESCRIPTION The /etc/ftpd/ftphosts file is used to allow or deny access to certain accounts from various hosts. Access Capabilities allow username addrglob [ addrglob ... ] Only allow host(s) matching addrglob to log in as username . addrglob is a globbed domain name or a globbed numeric address. deny username addrglob [ addrglob ... ] Always deny host(s) matching addrglob to log in as username .
ftpservers(4) ftpservers(4) NAME ftpservers - ftpd virtual hosting configuration specification file SYNPOSIS /etc/ftpd/ftpservers DESCRIPTION The /etc/ftpd/ftpservers file is used to tell which set of virtual domain configuration files that the ftpd server should use. With VIRTUAL support, wu-ftpd has the ability to use separate configuration files for each virtual domain. For a virtual host, configuration files can be placed into a separate virtual domain directory.
ftpusers(4) ftpusers(4) NAME ftpusers - security file for ftpd(1M) DESCRIPTION ftpd rejects remote logins to local user accounts that are named in /etc/ftpd/ftpusers. Each restricted account name must appear alone on a line in the file. The line cannot contain any white space. User accounts that specify a restricted login shell in /etc/passwd should be listed in /etc/ftpd/ftpusers because ftpd accesses local accounts without using their login shells. UUCP accounts should be listed in /etc/ftpd/ftpusers.
gated.conf(4) gated.conf(4) NAME gated.conf - GateDaemon configuration guide SYNOPSIS /etc/gated.
gated.conf(4) gated.conf(4) used to show optional keywords and parameters. The vertical bar (‘|’) is used to indicate between a choice of optional parameters. Parentheses (‘(’ and ‘)’) are used to group keywords and parameters when necessary. For example, in the syntax description: [ backbone | ( area area ) ] The square brackets say that either parameter is optional. The keywords are backbone and area. The vertical bar indicates that either ‘‘backbone’’ or ‘‘area area’’ may be specified.
gated.conf(4) generate (control) gated.conf(4) defines which routes to generate. Preference Preference is the value GateD uses to order preference of routes from one protocol or peer over another. Preference can be set in the GateD configuration files in several different configuration statements. Preference can be set based on network interface over another, from one protocol over another, or from one remote gateway over another.
gated.conf(4) gated.conf(4) aggregate/generate routes OSPF AS external routes BGP routes EGP aggregate/generate ospf bgp egp 130 150 170 200 Sample Preference Specifications interfaces { interface 138.66.12.2 preference 10 ; } ; rip yes { preference 90 ; } ; import proto rip gateway 138.66.12.1 preference 75 ; In these statements the preference applicable to routes learned via RIP from gateway 138.66.12.1 is 75. The last preference applicable to routes learned via RIP from gateway 128.66.12.
gated.conf(4) gated.conf(4) It is not currently possible to specify packet tracing from the command line. This is because a global option for packet tracing would potentially create too much output. When protocols inherit their tracing options from the global tracing options, tracing levels that do not make sense (such as parse, adv and packet tracing options) are masked out. Global tracing statements have an immediate effect, especially parsing options that effect the parsing of the configuration file.
gated.conf(4) gated.conf(4) current the directory, it just specifies the prefix applied to included file names. %include "filename" Identifies an include file. The contents of the file is included in the gated.conf file at the point in the gated.conf file where the %include directive is encountered. If the filename is not fully qualified (does not begin with "/"), it is considered to be relative to the directory defined in the %directory directive.
gated.conf(4) gated.
gated.conf(4) gated.conf(4) preference preference Sets the preference for routes to this interface when it is up and appears to be functioning properly. The default preference is 0. down preference preference Sets the preference for routes to this interface when GateD does not believe it to be functioning properly, but the kernel does not indicate it is down. The default value is 120.
gated.conf(4) gated.conf(4) multicast Specifies that the interface is multicast capable. Interface lists An interface list is a list of references to interfaces or groups of interfaces. There are four methods available for referring to interfaces. They are listed here from most general to most specific. all This refers to all available interfaces. Interface name wildcard This refers to all the interfaces of the same type.
gated.conf(4) gated.conf(4) If a subnet mask is specified on a point-to-point interface, it is only used by RIP version 1 and HELLO to determine which subnets may be propagated to the router on the other side of this interface. non-broadcast multi-access or nbma This type of interface is multi-access, but not capable of broadcast. And example would be frame relay and X.25. This type of interface has a local address and a subnet mask.
gated.conf(4) gated.conf(4) parameter may be specified to explicitly allow a subset of a range that was disallowed. Sample Definition Statements options gendefault ; autonomoussystem 249 ; interface 128.66.12.2 passive ; martians { 0.0.0.26 }; The statements in the sample perform the following functions: • The options statement tells the system to generate a default route when it peers with an EGP or BGP neighbor. • The autonomoussystem statement tells GateD to use AS number 249 for in EGP and BGP.
gated.conf(4) gated.conf(4) The EGP protocol is described in RFC 827 and RFC 904. BGP Border Gateway Protocol is replacing EGP as the exterior protocol of choice. BGP exchanges reachability information between autonomous systems, but provides more capabilities than EGP. BGP uses path attributes to provide more information about each route as an aid in selecting the best route.
gated.conf(4) gated.conf(4) Next hop The primary ones are the ability to advertise a next hop to use other than the router supplying the routing update. This is quite useful when advertising a static route to a dumb router that does not run RIP as it avoids having packets destined through the dumb router from having to cross a network twice. RIP I routers will ignore next hop information in RIP II packets. This may result in packets crossing a network twice, which is exactly what happens with RIP I.
gated.conf(4) gated.conf(4) [noripin] | [ripin] [noripout] | [ripout] [metricin metric] [metricout metric] [version 1]|[version 2 [multicast|broadcast]] [[secondary] authentication [none | [[simple|md5] password]] ; trustedgateways gateway_list ; sourcegateways gateway_list ; traceoptions trace_options ; }]; The rip statement enables or disables RIP. If the rip statement is not specified, the default is rip on ;.
gated.conf(4) gated.conf(4) ripout This is the default. This argument is necessary when it is desired to send RIP on pointto-point interfaces and may be necessary when noripin is used on a wildcard interface descriptor. metricin metric Specifies the RIP metric to add to incoming routes before they are installed in the routing table. The default is the kernel interface metric plus 1 (which is the default RIP hop count). If this value is specified, it will be used as the absolute value.
gated.conf(4) gated.conf(4) response RIP RESPONSE packets, which is the type of packet that actually contains routing information. other Any other type of packet. The only valid ones are TRACE_ON and TRACE_OFF both of which are ignored. The Hello Protocol It is really better not to use HELLO unless you have a specific need for it. We plan to drop it some time around GateD 4.0.
gated.conf(4) gated.conf(4) [nohelloin] | [helloin] [nohelloout] | [helloout] [metricin metric] [metricout metric] ; trustedgateways gateway_list ; sourcegateways gateway_list ; traceoptions trace_options ; }]; the hello statement enables or disables HELLO. If the hello statement is not specified, the default is hello off. If enabled, HELLO will assume nobroadcast when there is only one interface and broadcast when there is more than one interface.
gated.conf(4) gated.conf(4) metricout metric Specifies the HELLO metric to be added to routes that are send via the specified interface(s). The default is zero. This option is used to make other routers prefer other sources of HELLO routes over this router. trustedgateways gateway_list Defines the list of gateways from which HELLO will accept updates. The gateway_list is simply a list of host names or IP addresses. By default, all routers on the shared network are trusted to supply routing information.
gated.conf(4) gated.conf(4) OSPF uses the destination address and the type of service to choose the best route to the destination. OSPF intra- and inter-area routes are always imported into the GateD routing database with a preference of 10. It would be a violation of the protocol if an OSPF router did not participate fully in the OSPF of the area, so it is not possible to override this. Although it is possible to give other routes lower preference values explicitly, it is ill-advised to do so.
gated.conf(4) gated.conf(4) }; interface interface_list nonbroadcast [cost cost ] { pollinterval time ; routers { gateway [ eligible ] ; }; interface_parameters }; Backbone only: virtuallink neighborid router_id transitarea area { interface_parameters }; }; }]; The following are the interface_parameters referred to above. The may be specified on any class of interface and are described under the interface clause.
gated.conf(4) gated.conf(4) utility sends non-standard OSPF packets which generate a text response from OSPF. By default these requests are not authenticated, if an authentication key is configured, the incoming requests must match the specified authentication key. No OSPF state may be changed by these packets, but the act of querying OSPF can utilize system resources. backbone area area Each OSPF router must be configured into at least one OSPF area.
gated.conf(4) gated.conf(4) hellointerval time The length of time, in seconds, between Hello packets that the router sends on the interface. routerdeadinterval time The number of seconds not hearing Hello packets of a router before the neighbors of the router will declare it down. authkey auth_key Used by OSPF authentication to generate and verify the authentication field in the OSPF header. The authentication key can be configured on a per interface basis.
gated.conf(4) gated.conf(4) request OSPF Link State Request packets which are used in synchronizing OSPF databases. lsu OSPF Link State Update packets which are used in synchronizing OSPF databases. ack OSPF Link State Ack packets which are used in synchronizing OSPF databases. The Exterior Gateway Protocol (EGP) The Exterior Gateway Protocol (EGP) is an exterior routing protocol used for exchanging routing information with gateways in other autonomous systems.
gated.conf(4) gated.conf(4) packetsize maxpacketsize This defines the expected maximum size of a packet that EGP expects to receive from this neighbor. If a packet larger than this value is received, it will be incomplete and have to be discarded. The length of this packet will be noted and the expected size will be increased to be able to receive a packet of this size. Specifying the parameter here will prevent the first packet from being dropped. If not specified, the default size is 8192 bytes.
gated.conf(4) gated.conf(4) ignored. For efficiency, some networks have external routers announce a default route to avoid sending large EGP update packets. exportdefault Enables GateD to include the default route (0.0.0.0) in EGP updates sent to this EGP neighbor. This allows the system to advertise the default route via EGP. Normally a default route is not included in EGP updates.
gated.conf(4) gated.conf(4) update EGP POLL/UPDATE packets which are used to request and receive reachability updates. The BGP Protocol The Border Gateway Protocol (BGP) is an exterior routing protocol used for exchanging routing information between autonomous systems. BGP is used for exchange of routing information between multiple transit autonomous systems as well as between transit and stub autonomous systems.
gated.conf(4) gated.conf(4) that the BGP routes will only be used to determine the path attributes associated with the IGP routes. Such groups also support distant peers, and also need to be informed of the IGP they are running with. For internal BGP group types (and for test groups), where possible a single outgoing message is built for all group peers based on the common policy.
gated.conf(4) gated.conf(4) preference preference Sets the preference for routes learned from RIP. The default preference is 170. This preference may be overridden by a preference specified on the group or peer statements or by import policy. defaultmetric metric Defines the metric used when advertising routes via BGP. If not specified, no metric is propagated. This metric may be overridden by a metric specified on the neighbor or group statements or in export policy.
gated.conf(4) gated.conf(4) the next hop is the current next hop of the local machine. All routing information advertised by and received from a test peer is discarded, and all BGP routes that can be advertised are sent back to the test peer. Metrics from EGP-derived and BGP-derived routes are forwarded in the advertisement. Otherwise no metric is included. Group parameters The BGP statement has group clauses and peer subclauses. Any number of peer subclauses may be specified within a group.
gated.conf(4) gated.conf(4) will only be opened when an interface with the appropriate local address (through which the peer or gateway address is directly reachable) is operating. For other types of peers, a peer session will be maintained when any interface with the specified local address is operating. In either case incoming connections will only be recognized as matching a configured peer if they are addressed to the configured local address.
gated.conf(4) gated.conf(4) routes on to version 3 neighbors. logupdown Causes a message to be logged via the syslog mechanism whenever a BGP peer enters or leaves the ESTABLISHED state. ttl ttl By default, GateD sets the IP TTL for local peers to one and the TTL for non-local peers to 255. This option mainly is provided when attempting to communicate with improperly functioning routers that ignore packets sent with a TTL of one. Not all kernels allow the TTL to be specified for TCP connections.
gated.conf(4) gated.conf(4) Redirect Processing The redirect code is passed ICMP or ISO redirects learned by monitoring ICMP messages, or via the routing socket on systems that support it. It processes the redirect request and decides whether to accept the redirect. If the redirect is accepted, a route is installed in the gated routing table with the protocol redirect . Redirects are deleted from the routing table after 3 minutes.
gated.conf(4) gated.conf(4) Tracing options There are no Redirect -specific tracing options. All non-error messages are traced under the normal class. The Router Discovery Protocol The Router Discovery Protocol is an IETF standard protocol used to inform hosts of the existence of routers. It is intended to be used instead of having hosts wiretap routing protocols such as RIP. It is used in place of, or in addition to statically configured default routes in hosts.
gated.conf(4) gated.conf(4) minadvinterval time The minimum time allowed between sending unsolicited broadcast or multicast Router Advertisements from the interface. Must be no less than 3 seconds and no greater than maxadvinterval. The default is 0.75 * maxadvinterval. lifetime time The lifetime of addresses in a Router Advertisement. Must be no less than maxadvinterval and no greater than 2:30:00 (two hours, thirty minutes or 9000 seconds). The default is 3 * maxadvinterval.
gated.conf(4) gated.conf(4) When a Router Advertisement with a zero lifetime is received, the host deletes all routes with next-hop addresses learned from that router. In addition, any routers learned from ICMP redirects pointing to these addresses will be deleted. The same will happen when a Router Advertisement is not received to refresh these routes before the lifetime expires.
gated.conf(4) gated.conf(4) many more routes. The speed of the kernel interface becomes critical when these protocols are used. To prevent GateD from locking up for significant periods of time installing large numbers of routes (up to a minute or more has been observed on real networks), the processing of these routes is now done in batches. The size of these batches may be controlled by the tuning parameters described below, but normally the default parameters will provide the proper functionality.
gated.conf(4) gated.conf(4) no longer needs to monitor ICMP messages to learn about redirects. Plus, there is an indication of whether the kernel processed the redirect, GateD can safely ignore redirect messages that the kernel did not process. Updates visible Changes to the routing table by other processes, including the route command are received via the routing socket. This allows GateD to insure that the kernel forwarding table is in sync with the routing table.
gated.conf(4) gated.conf(4) GateD reads re-reads this list every 15 second looking for changes. When the routing socket is in use, it also re-reads it whenever a messages is received indicating a change in routing configuration. Receipt of a SIGUSR2 signal also causes GateD to re-read the list. This interval may be explicitly configured in the interface configuration. Reading the interface list with sysctl BSD 4.4 added the ability to read the kernel interface list via the sysctl system call.
gated.conf(4) gated.conf(4) flash [ limit number ] [ type interface | interior | all ] ; background [ limit number ] [ priority flash | higher | lower ] ; traceoptions trace_options ; }; options option_list Configure kernel options. The valid options are: nochange On systems supporting the routing socket this insures that changes operations will not be performed, only deletes and adds. This is useful on early versions of the routing socket code where the change operation was broken.
gated.conf(4) gated.conf(4) are processed in batches in the background, that is, when no routing protocol traffic is being received. Normally, 120 routes are installed at a time to allow other tasks to be performed and this background processing is done at lower priority than flash updates the following parameters allow tuning of these parameters: limit number Specifies the number of route which may be processed at during one batch. The default is 120.
gated.conf(4) gated.conf(4) limited by the number of multipath destinations supported (this compile time parameter is currently almost always one on Unix). Parameters for static routes are: interface interface_list When this parameter is specified, gateways are only considered valid when they are on one of these interfaces.See the section on interface list specification for the description of the interface_list. preference preference This option selects the preference of this static route.
gated.conf(4) gated.conf(4) default host host These are all the possible formats for a route filter. Not all of these formats are available in all places, for instance the host and default formats are not valid for martians . In most cases it is possible to specify additional parameters relevant to the context of the filter. For example, on a martian statement it is possible to specify the allow keyword, on an import statement you can specify a preference, and on a export you can specify a metric.
gated.conf(4) gated.conf(4) aspath aspath_regexp origin any | ( [ igp ] [egp ] [ incomplete ] ) This specifies that an AS matching the aspath_regexp with the specified origin is matched. AS path regular expressions Technically, an AS path regular expression is a regular expression with the alphabet being the set of AS numbers. An AS path regular expression is composed of one or more AS paths expressions. An AS path expressions is composed of AS path terms and AS path operators.
gated.conf(4) gated.conf(4) restrict Specifies that the routes are not desired in the routing table. In some cases this means that the routes are not installed in the routing table. In others it means that they are installed with a negative preference; this prevents them from becoming active so they will not be installed in the forwarding table, or exported to other protocols. preference preference Specifies the preference value used when comparing this route to other routes from other protocols.
gated.conf(4) gated.conf(4) The importation of RIP, HELLO and Redirect routes may be controlled by any of protocol, source interface and source gateway. If more than one is specified, they are processed from most general (protocol) to most specific (gateway). RIP and HELLO do not support the use of preference to choose between routes of the same protocol. That is left to the protocol metrics. These protocols do not save routes that were rejected since they have short update intervals.
gated.conf(4) gated.conf(4) default host host Specifying the destination As mentioned above, the syntax of the export statement varies depending on the protocol it is being applied to. One thing that applies in all cases is the specification of a metric. All protocols define a default metric to be used for routes being exported, in most cases this can be overridden at several levels of the export statement.
gated.conf(4) gated.conf(4) [ metric metric ] { export_list ; }; It is not possible to create OSPF intra- or inter-area routes by exporting routes from the GateD routing table into OSPF. It is only possible to export from the GateD routing table into OSPF ASE routes. It is also not possible to control the propagation of OSPF routes within the OSPF protocol. There are two types of OSPF ASE routes, type 1 and type 2, see the OSPF protocol configuration for a detailed explanation of the two types.
gated.conf(4) gated.conf(4) direct Routes to directly attached interfaces. static Static routes specified in a static clause. kernel On systems with the routing socket, routes learned from the routing socket are installed in the GateD routing table with a protocol of kernel. These routes may be exported by referencing this protocol. This is useful when it is desirable to have a script install routes with the route command and propagate them to other routing protocols.
gated.conf(4) gated.conf(4) Route aggregation is also used by regional and national networks to reduce the amount of routing information passed around. With careful allocation of network addresses to clients, regional networks can just announce one route to regional networks instead of hundreds. Aggregate routes are not actually used for packet forwarding by the originator of the aggregate route, only by the receiver (if it wishes).
gated.conf(4) gated.conf(4) as autonomous_system Restrict selection of routes to those learned from the specified autonomous system. tag tag Restrict selection of routes to those with the specified tag. aspath aspath_regexp Restrict selection of routes to those that match the specified AS path. restrict Indicates that these routes are not to be considered as contributors of the specified aggregate. The specified protocol may be any of the protocols supported by GateD. route_filter See below.
gated.conf(4) gated.conf(4) distance An EGP metric. See metric. Valid values are from zero to 255 inclusive. egp exterior gateway protocol exterior routing protocol A class of routing protocols used to exchange routing information within an autonomous system. A detailed explanation of exterior gateway protocols is available in the Protocol Overview. EGP Exterior Gateway Protocol One of a class of exterior gateway protocols, described in more detail in the EGP section of the Protocol Overview.
gated.conf(4) gated.conf(4) which bits of the destination are significant. Except when used in a route filter, GateD only supports contiguous masks. mask length The number of significant bits in the mask. metric One of the units used to help a system determine the best route. Metrics may be based on hop count, routing delay, or an arbitrary value set by the administrator depending on the type of routing protocol. Routing metrics may influence the value of assigned internal preferences. (See preference.
gated.conf(4) gated.conf(4) Peers are usually on a shared network, but not always. This term is mostly used by BGP. Usually synonymous with neighbor. port A UDP or TCP port number. Valid values are from 1 through 65535 inclusive. preference A preference is a value between 0 (zero) and 255 used to select between many routes to the same destination. The route with the best (numerically lowest) preference is as the active route.
gated.conf(4) ttl gated.conf(4) The Time To Live (TTL) of an IP packet. Valid values are from one (1) through 255 inclusive. TOS type of service The type of service is for internet service quality selection. The type of service is specified along the abstract parameters precedence, delay, throughput, reliability, and cost. These abstract parameters are to be mapped into the actual service parameters of the particular networks the datagram traverses.
gettydefs(4) gettydefs(4) NAME gettydefs - speed and terminal settings used by getty DESCRIPTION The /etc/gettydefs file contains information used by getty to set up the speed and terminal settings for a line (see getty (1M)). It supplies information on what the login prompt should look like. It also supplies the speed to try next if the user indicates the current speed is not correct by typing a Break character.
group(4) group(4) NAME group, logingroup - group file, grp.h DESCRIPTION group contains for each group the following information: • group name • encrypted password • numerical group ID • comma-separated list of all users allowed in the group This is an ASCII file. Fields are separated by colons, and each group is separated from the next by a new-line. No spaces should separate the fields or parts of fields on any line. If the password field is null, no password is associated with the group.
group(4) group(4) There is no single tool available to completely ensure that /etc/passwd, /etc/group, and /etc/logingroup are compatible. However, pwck and grpck can be used to simplify the task (see pwck (1M)). There is no tool for setting group passwords in /etc/group.
hosts(4) hosts(4) NAME hosts - host name data base DESCRIPTION The file /etc/hosts associates Internet (IP) addresses with official host names and aliases. This allows a user to refer to a host by a symbolic name instead of an Internet address. Note : This file must contain all addresses for local interfaces that ifconfig needs at boot time (see ifconfig(1M)).
hosts.equiv(4) hosts.equiv(4) NAME hosts.equiv, .rhosts - security files authorizing access by remote hosts and users on local host DESCRIPTION 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)).
hosts.equiv(4) hosts.equiv(4) name (only) must match the specified network group according to the rules defined in netgroup (4) in order for the host name to match. Similarly, if the user name in hostequiv is of this form, the remote user name (only) must match the specified network group in order for the user name to match. -@netgroup_name netgroup_name is the name of a network group as defined in netgroup (4).
hosts.equiv(4) hosts.equiv(4) + -chm hostB Any user from hostB except chm is allowed to access an account on hostA with the same user name. However, if .rhosts in the home directory of user chm on hostA contains: hostB then user chm from hostB can access account chm on hostA. 6. /etc/hosts.
inetd.conf(4) inetd.conf(4) NAME inetd.conf - configuration file for inetd DESCRIPTION On invocation, the inetd daemon reads its configuration information from the /etc/inetd.conf configuration file, and possibly at some later time in response to a SIGHUP signal (see inetd (1M)). Each line in the file is treated either as a comment or as configuration information for a given service Comments are denoted by a # at the beginning of a line.
inetd.conf(4) inetd.conf(4) program number Defines a particular service grouping and is unique. version number Version supported by the RPC service. This number can be a single value, or a range, if the program handles multiple versions; for example, 1 or 1-3. Ranges are separated by a hyphen (-). Version numbers allow RPC protocols to be extended and modified, and make it possible for old and new protocols to share the same server process.
inetd.sec(4) inetd.sec(4) NAME inetd.sec - optional security file for inetd DESCRIPTION When inetd accepts a connection from a remote system, it checks the address of the host requesting the service against the list of hosts to be allowed or denied access to the specific service (see inetd (1M)). The file inetd.sec allows the system administrator to control which hosts (or networks in general) are allowed to use the system remotely.
inetd.sec(4) inetd.sec(4) Allow access to the shell service by any host: shell allow or shell IPv6 FUNCTIONALITY For an IPv6 service, an IPv6 address can be specified in the host address field of inetd.sec. The host address field can contain IPv6 addresses, IPv4 addresses, or both. This specification includes the IPv4 mapped IPv6 addresses also. Host names for IPv6 services are the official names of the hosts returned by getaddrinfo().
inetsvcs.conf(4) inetsvcs.conf(4) NAME inetsvcs.conf - configuration file for secure internet services DESCRIPTION The internet services, ftp, rcp, remsh, rlogin and telnet, use the /etc/inetsvcs.conf configuration file to decide their behavior (i.e., whether to allow network authentication using Kerberos V5 or not). The contents of the file decide whether the secure internet services are to be enabled or not. This configuration file is updated by the program inetsvcs_sec.
info(4) info(4) NAME info - diskless client configuration information file DESCRIPTION The info file is a POSIX shell sourceable file which contains parameter definitions used at boot time. Typically, it will be an empty file and default values will be used for all parameters. Following is the list of parameters which can be defined in the info file: ROOT_SERVER_IP Specifies the IP address of the client’s private root server.
inittab(4) inittab(4) NAME inittab - script for the boot init process DESCRIPTION The /etc/inittab file supplies the script to the boot init daemon in its role as a general process dispatcher (see init (1M)). The process that constitutes the majority of boot init’s process dispatching activities is the line process /usr/sbin/getty that initiates individual terminal lines. Other processes typically dispatched by boot init are daemons and shells.
inittab(4) inittab(4) rstate field is empty, boot init enters run level 6. The initdefault entry cannot specify that boot init start in the single-user state. Additionally, if boot init does not find an initdefault entry in inittab, it requests an initial run level from the user at boot time. process off If the process associated with this entry is currently running, send the warning signal (SIGTERM) and wait 20 seconds before forcibly terminating the process via the kill signal (SIGKILL).
inode_vxfs(4) inode_vxfs(4) NAME inode_vxfs - format of a VxFS file system inode SYNOPSIS #include #include DESCRIPTION A VxFS inode is typically 256 bytes in length, but an inode can also be 512 bytes. You specify the inode size with mkfs. An inode entry has the following format: A iA i_mode The mode and type of file. i_nlink The number of links to the file. i_uid The inode owner. i_gid The inode group. i_size The size in bytes of the file.
inode_vxfs(4) inode_vxfs(4) For directories, the following field is supported: The parent directory inode inumber if the inode is a directory. This replaces the standard ‘‘..’’ (dot dot) entry in the first directory block. VxFS does not have explicit ‘‘.’’ (dot ) and ‘‘..’’ (dot dot) entries. i_dotdot For regular files, the following fields are supported: i_reserve The number of data blocks reserved for exclusive use by the file (preallocation). A preallocation can be requested using an ioctl.
inode_vxfs(4) inode_vxfs(4) The remaining bytes of the inode are reserved for extended attribute records. Their format is: length The length of the attribute record. If this is not a multiple of 4 bytes, the start of the next attribute record is found by rounding the length up to a 4 byte boundary. format The format of the data layout of the remainder record.
ioconfig(4) ioconfig(4) NAME ioconfig - ioconfig entry format SYNOPSIS #include DESCRIPTION The ioconfig file is used to retain information on system’s IO configuration across reboots. It contains two types of information: • Mappings of dynamically allocated major numbers to drivers. • Mappings of instance numbers to hardware paths. At boot time this file is read and the information is stored in the io_tree kernel data structure.
ioconfig(4) ioconfig(4) typedef struct dyn_major { char rec_name[MAX_NAME_LEN]; char name[MAX_NAME_LEN]; int c_major; int b_major; int reserved; /* Must be _DYN_MAJOR" */" /* Driver name */ } dyn_major_t; AUTHOR ioconfig was developed by HP. FILES /etc/ioconfig /stand/ioconfig SEE ALSO ioscan(1M), ioinit(1M), insf(1M), rmsf(1M), magic(4).
issue(4) issue(4) NAME issue - issue identification file DESCRIPTION The file /etc/issue contains the issue or project identification to be printed as a login prompt. This is an ASCII file which is read by the getty program then written to any terminal spawned or respawned from the inittab file. FILES /etc/issue SEE ALSO getty(1M), login(1).
krb5.conf(4) krb5.conf(4) NAME krb5.conf - Kerberos configuration file DESCRIPTION The configuration file, krb5.conf, contains information needed by the Kerberos V5 library. This includes information describing the default Kerberos realm and the location of the Kerberos key distribution centers for known realms. The krb5.conf file uses an INI-style format. Sections are delimited by square braces, [ ]. Within each section, there are relations where tags can be assigned to have specific values.
krb5.conf(4) krb5.conf(4) default_tkt_enctypes This relation identifies the supported list of session key encryption types that should be requested by the client, in the same format. clockskew This relation sets the maximum allowable amount of clockskew in seconds that the library will tolerate before assuming that a Kerberos message is invalid. The default value is 300 seconds, or five minutes.
krb5.conf(4) krb5.conf(4) mit = mit.edu lithium = lithium.lcs.mit.edu } } For each realm, the following tags may be specified in the realm’s subsection: kdc The value of this relation is the name of a host running a Key Distribution Center for that realm. An optional port number (preceded by a colon) may be appended to the hostname. admin_server This relation identifies the host where the administration server is running. Typically this is the Master Kerberos server.
krb5.conf(4) krb5.conf(4) DEVICE=devicename This causes the entity’s logging messages to go to the specified device. SYSLOG[:severity [:facility ]] This causes the entity’s logging messages to go to the system log. The severity argument specifies the default severity of system log messages. This may be any of the following severities mentioned below supported by the syslog() call (see the syslog (3C) manual page).
krb5.conf(4) krb5.conf(4) ANL.GOV = ES.NET } ES.NET = { ANL.GOV = . } The [capaths] section of the configuration file used on NERSC.GOV systems would look like this: A [capaths] NERSC.GOV = { ANL.GOV = ES.NET TEST.ANL.GOV = ES.NET TEST.ANL.GOV = ANL.GOV PNL.GOV = ES.NET ES.NET = . } ANL.GOV = { NERSC.GOV = ES.NET } PNL.GOV = { NERSC.GOV = ES.NET } ES.NET = { NERSC.GOV = . } TEST.ANL.GOV = { NERSC.GOV = ANL.GOV NERSC.GOV = ES.
libgss(4) libgss(4) NAME libgss - shared library for GSSAPI (Generic Security Service Application Programming Interface) SYNOPSIS #include /usr/lib/libgss.sl DESCRIPTION libgss is a shared library which contains all the GSSAPIs as per the RFC 2743 and implemented as Clanguage interfaces as defined in the RFC 2744, Generic Security Service API : C-bindings. GSSAPI provides security services for applications independent of the various underlying security mechanisms.
libgss(4) libgss(4) # files Using the GSSAPI framework Applications communicating using the GSSAPI framework go through the following main stages: 1. The communicating applications acquire a set of credentials to prove their identity to other applications. The applications’ credentials vouch for their global identities. 2. The applications establish a joint security context using their credentials. This information is used to provide per message security services like integrity and confidentiality.
libgss(4) libgss(4) gss_wrap: To encrypt a message for Confidentiality Service. gss_unwrap: To decrypt a message for Confidentiality Service. Name Manipulation APIs Names identify principals. Names are represented in printable form (for presentation to an application) or in internal for (canonical form) that is used by the API and is opaque to applications. The following are the APIs that are used manipulate the names: gss_import_name: Convert a contiguous string name to a internal form.
lif(4) lif(4) NAME lif - logical interchange format description DESCRIPTION LIF (Logical Interchange Format) is a Hewlett-Packard standard mass-storage format that can be used for interchange of files among various HP computer systems. A LIF volume contains a header (identifying it as a LIF volume) and a directory that defines the contents (i.e. files) of the volume.
lif(4) lif(4) Do not mount the special file while using lif ∗(1) utilities . SEE ALSO lifcp(1), lifinit(1), lifls(1), lifrename(1), lifrm(1).
localedef(4) localedef(4) NAME localedef - format and semantics of locale definition file DESCRIPTION This is a description of the syntax and meaning of the locale definition that is provided as input to the localedef command to create a locale (see localedef (1M)). The following is a list of category tags, keywords and subsequent expressions which are recognized by localedef.
localedef(4) localedef(4) characters, with each set in ascending order. alpha Character codes classified as letters. Characters classified as cntrl, digit, punct or space cannot be specified. Characters specified as upper and lower classes are automatically included in this class. print Character codes classified as printable characters. Characters specified for upper, lower, alpha, digit, xdigit, and punct classes and the character are automatically included.
localedef(4) localedef(4) forward Specifies that comparison operations proceed from start of string towards the end of it. backward Specifies that comparison operations proceed from end of string towards the beginning of it. order_end Marks the end of the list of collating element entries. LC_MONETARY: The LC_MONETARY category defines the rules and symbols used to format monetary numeric information.
localedef(4) localedef(4) p_sign_posn The operand is an integer which setting indicates the positioning of the positive_sign for a non-negative monetary quantity. The possible values are: 0 Parenthesis surround the quantity and the currency_symbol or int_curr_symbol. 1 The sign string precedes the quantity and the and the currency_symbol or int_curr_symbol. 2 The sign string succeeds the quantity currency_symbol or int_curr_symbol.
localedef(4) localedef(4) t_fmt The operand is a string defining the appropriate time representation. am_pm The operand is two semicolon-separated strings giving the representations for AM and PM. t_fmt_ampm The operand is a string defining the appropriate time representation in the 12-hour clock format with am_pm. era The operand is a semi-colon-separated list of strings. Each string defines the name and date of an era or emperor for a locale.
localedef(4) localedef(4) mon_unit, day_unit, rour_unit, min_unit, sec_unit. LC_MESSAGES: The LC_MESSAGES category defines the format and values for affirmative and negative responses. The following keywords belong to this category and should come between the category tag LC_MESSAGES and END LC_MESSAGES: yesexpr The string operand is an Extended Regular Expression matching acceptable affirmative responses to yes/no queries.
localedef(4) localedef(4) octal constants An escape character followed by up to three octal digits. hexadecimal constants An escape character followed by a ’x’ followed by two hexadecimal digits. character constants A single character (e.g., A) having the numerical value of the character in the machine’s character set. symbolic names A string enclosed between < and > is a symbolic name.
localedef(4) localedef(4) An equivalence class is defined by a series of collating element entries all having the same character or symbol in the first weight position. For example, in many locales all forms of the character ’A’ collate equal on the first pass.
localedef(4) localedef(4) Comments Comments are lines beginning with a comment character. The comment character is pound sign (#) by default, but can be redefined by the comment_char keyword. Comments and blank lines are ignored. Separators Separator characters include blanks and tabs.
lvmpvg(4) lvmpvg(4) NAME lvmpvg - LVM physical volume group information file SYNOPSIS /etc/lvmpvg DESCRIPTION lvmpvg is an ASCII file that stores the volume-group information for all of the physical volume groups in the system. The information is stored in a hierarchical format. First, it starts with a volume group under which multiple physical volume groups can exist. Under each physical volume group, a list of physical volumes can be specified.
lvmpvg(4) lvmpvg(4) SEE ALSO vgcreate(1M), vgextend(1M), vgreduce(1M), vgremove(1M).
magic(4) magic(4) NAME magic - magic numbers for HP-UX implementations SYNOPSIS #include DESCRIPTION The magic.h file localizes all information about HP-UX ‘‘magic numbers’’ in one file, thus facilitating uniform treatment of magic numbers. This file specifies the location of the magic number in a file (always the start of the file) and the structure of the magic number: struct magic_number { unsigned short system_id; unsigned short file_type; }; typedef struct magic_number MAGIC; magic.
mnttab(4) mnttab(4) NAME mnttab - mounted file system table SYNOPSIS #include DESCRIPTION mnttab resides in directory /etc and contains a table of devices mounted by the mount command (see mount (1M)). The file contains a line of information for each mounted filesystem which is structurally identical to the contents of /etc/fstab described by fstab (4).
model(4) model(4) (TO BE OBSOLETED) NAME model - HP-UX machine identification SYNOPSIS #include DESCRIPTION There are certain inevitable distinctions between HP-UX implementations due to hardware differences. Where such distinctions exist, conditional compilation or other definitions can be used to isolate the differences. Flags and typedefs to resolve these distinctions are collected in the header file which contains constants identifying various HP-UX implementations.
named.conf(4) named.conf(4) NAME named.conf - configuration file for NameDaemon SYNOPSIS /etc/named.conf DESCRIPTION BIND 9 configuration is broadly similar to BIND 8.x. However, there are a few new areas of configuration, such as views. BIND 8.x configuration files should work with few alterations in BIND 9.2, although more complex configurations need to be reviewed to check if they can be more efficiently implemented using the new features implemented in BIND 9.2. BIND 4.9.
named.conf(4) named.conf(4) Address Match Lists Syntax address_match_list3D address_match_list_element ; [ address_match_list_element; ... ] address_match_list_element3D [ ! ] (ip_address [/length ] | key key_id | acl_name | { address_match_list } ) Address Match Lists Definition and Usage Address match lists are primarily used to determine access control for various server operations.
named.conf(4) named.conf(4) trusted-keys defines trusted DNSSEC keys. view defines a view. zone defines a zone. The logging and options statements may occur only once per configuration. acl Statement Grammar acl acl-name { address_match_list }; acl Statement Definition and Usage The acl statement assigns a symbolic name to an address match list. It gets its name from the primary use of address match lists: "Access Control Lists" (ACLs).
named.conf(4) named.conf(4) The UNIX control channel type of BIND 8 is not supported in BIND 9.2, and is not expected to be added in future releases. If it is present in the controls statement from a BIND 8 configuration file, it is ignored and a warning is logged. include Statement Grammar include filename ; include Statement Definition and Usage The include statement inserts the specified file at the point where the include statement is encountered.
named.conf(4) named.conf(4) }; In BIND 9.2, the logging configuration is established only when the entire configuration file has been parsed. In BIND 8, it was established as soon as the logging statement was parsed. When the server starts up, all logging messages related to syntax errors in the configuration file go to the default channels, or to standard error if the -g option was specified.
named.conf(4) named.conf(4) trace. The global debug level can be set to zero, and debugging mode turned off, by running rndc notrace. All debugging messages in the server have a debug level, and higher debug levels give more detailed output.
named.conf(4) named.conf(4) in that category will be sent to the default category instead.
named.conf(4) named.conf(4) [ search { domain_name ; [ domain_name ; ... ] }; ] [ ndots number; ] }; lwres Statement Definition and Usage The lwres statement configures the name server to also act as a lightweight resolver server. There may be be multiple lwres statements configuring lightweight resolver servers with different properties. The listen-on statement specifies a list of addresses and ports that a lightweight resolver daemon should accept requests on. If no port is specified, port 921 is used.
named.conf(4) [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ A nA named.conf(4) transfer-source-v6 (ip6_addr | *) [port ip_port] ; ] notify-source (ip4_addr | *) [port ip_port] ; ] notify-source-v6 (ip6_addr | *) [port ip_port] ; ] also-notify { ip_addr [port ip_port] ; [ ip_addr [port ip_port] ; ...
named.conf(4) named.conf(4) statistics-file The pathname of the file in which the server appends statistics using rndc stats. Default is named.stats in the server’s current directory. port The UDP/TCP port number the server uses for receiving and sending DNS protocol traffic. Default is 53. This option is mainly intended for server testing; a server using a port other than 53 will not be able to communicate with the global DNS. random-device The source of entropy to be used by the server.
named.conf(4) named.conf(4) zone-statistics If "yes", the server will, by default, collect statistical data on all zones in the server. These statistics may be accessed using rndc stats, which will dump them to the file listed in the statistics-file. provide-ixfr clause determines whether the local server, acting as master, will respond with an incremental zone transfer when the given remote server, a slave, requests it. If set to "yes", incremental transfer will be provided whenever possible.
named.conf(4) named.conf(4) Forwarding can also be configured on a per-domain basis, allowing for the global forwarding options to be overridden in a variety of ways. You can set a particular domain to use different forwarders, or have a different forward only/first: behavior, or not forward at all. Access Control Access to the server can be restricted based on the IP address of the requesting system.
named.conf(4) named.conf(4) If no listen-on-v6 statement is specified, the server will not listen on any IPv6 address. Query Address If the server is unable to answer a question, it will query other nameservers. query-source specifies the address and port used for such queries. For queries sent over IPv6, there is a separate querysource-v6 option. If address is * or is omitted, a wildcard IP address (INADDR_ANY) will be used. If port is * or is omitted, a random unprivileged port will be used.
named.conf(4) named.conf(4) transfers-per-ns The maximum number of concurrently running inbound zone transfers from a given remote nameserver. Default value is 2. Increasing transfers-per-ns may speed up the convergence of slave zones, but it also may increase the load on the remote nameserver. transfers-per-ns may be overridden on a per-server basis by using the transfers phrase of the server statement.
named.conf(4) named.conf(4) Default is 100. max-cache-size The maximum amount of memory to use for the server’s cache, in bytes. When the amount of data in the cache reaches this limit, the server will cause records to expire prematurely so that the limit is not exceeded. In a server with multiple views, the limit applies separately to the cache of each view. Default is unlimited, meaning that records are purged from the cache only when their TTLs expire.
named.conf(4) named.conf(4) { 192.168.2/24; // IF on class C 192.168.2 { 192.168.2/24; // THEN use .2, or .1 or .3 { 192.168.1/24; 192.168.3/24; }; }; }; { 192.168.3/24; // IF on class C 192.168.3 { 192.168.3/24; // THEN use .3, or .1 or .2 { 192.168.1/24; 192.168.2/24; }; }; }; { { 192.168.4/24; 192.168.5/24; }; // if .4 or .5, prefer that net }; }; The following example will give reasonable behavior for the local host and hosts on directly connected networks.
named.conf(4) named.conf(4) min-refresh-time, max-refresh-time, min-retry-time, max-retry-time These options control the server’s behavior on refreshing a zone (querying for SOA changes) or retrying failed transfers. Usually the SOA values for the zone are used, but these values are set by the master, giving slave server administrators little control over their contents. These options allow the administrator to set a minimum and maximum refresh and retry time either per-zone, per-view, or per-server.
named.conf(4) named.conf(4) it possible to disable the use of IXFR even when both master and slave claim to support it, for example if one of the servers is defective and crashes or corrupts data when IXFR is used. The edns (Extended DNS) clause determines whether the local server will attempt to use EDNS when communicating with the remote server. Default is "yes". The server supports two zone transfer methods. The first, one-answer, uses one DNS message per resource record transferred.
named.conf(4) named.conf(4) Many of the options given in the options statement can also be used within a view statement, and then apply only when resolving queries with that view. When no view-specific value is given, the value in the options statement is used as a default. Also, zone options can have default values specified in the view statement; these view-specific defaults take precedence over those in the options statement. Views are class-specific. If no class is given, class IN is assumed.
named.conf(4) [ [ [ [ [ [ [ [ [ named.conf(4) notify-source (ip4_addr | *) [port ip_port] ; ] notify-source-v6 (ip6_addr | *) [port ip_port] ; ] zone-statistics yes_or_no ; ] sig-validity-interval number ; ] database string ; ] min-refresh-time number ; ] max-refresh-time number ; ] min-retry-time number ; ] max-retry-time number ; ] }]; zone Statement Definition and Usage Zone Types master The server has a master copy of the data for the zone and will be able to provide authoritative answers for it.
named.conf(4) named.conf(4) development is CHAOSnet, a LAN protocol created in the mid-1970s. Zone data for it can be specified with the CHAOS class. Zone Options allow-notify See the description of allow-notify. allow-query See the description of allow-query. allow-transfer See the description of allow-transfer. allow-update Specifies which hosts are allowed to submit Dynamic DNS updates for master zones. The default is to deny updates from all hosts.
named.conf(4) notify named.conf(4) See the description of notify above. zone-statistics If yes, the server will keep statistical information for this zone, which can be dumped to the statistics-file defined in the server options. sig-validity-interval See the description of sig-validity-interval. transfer-source See the description of transfer-source. transfer-source-v6 See the description of transfer-source-v6. notify-source See the description of notify-source.
named.conf(4) named.conf(4) Resource Records A domain name identifies a node. Each node has a set of resource information, which may be empty. The set of resource information associated with a particular name is composed of separate RRs. The order of RRs in a set is not significant and need not be preserved by nameservers, resolvers, or other parts of the DNS. However, sorting of multiple RRs is permitted for optimization purposes, for example, to specify that a particular nearby server be tried first.
named.conf(4) NS a fully qualified domain name. PTR a fully qualified domain name. SOA several fields. named.conf(4) The owner name is often implicit, rather than forming an integral part of the RR. For example, many nameservers internally form tree or hash structures for the name space, and chain RRs off nodes. The remaining RR parts are the fixed header (type, class, TTL) which is consistent for all RRs, and a variable part (RDATA) that fits the needs of the resource being described.
named.conf(4) named.conf(4) name. The domain name given is the machine to which the mail will be delivered. It must have an associated A record - CNAME is not sufficient. For a given domain, if there is both a CNAME record and an MX record, the MX record is in error, and will be ignored. Instead, the mail will be delivered to the server specified in the MX record pointed to by the CNAME. example.com.INMX10mail.example.com. INMX10mail2.example.com. INMX20mail.backup.org. mail.example.com.INA10.0.0.1 mail2.
named.conf(4) named.conf(4) WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. The $INCLUDE Directive Syntax: $INCLUDE filename [origin] [comment ] Read and process the file filename as if it were included into the file at this point. If origin is specified the file is processed with $ORIGIN set to that value, otherwise the current $ORIGIN is used.
named.conf(4) named.conf(4) AUTHOR named.conf was developed by Internet Software Consortium (ISC). SEE ALSO kill(1), hosts_to_named(1M), sig_named(1M), signal(2), gethostent(3N), resolver(3N), resolver(4), hostname(5), RFC 882, RFC 883, RFC 973, RFC 974, RFC 1032, RFC 1033, RFC 1034, RFC 1035, RFC 1123.
netconfig(4) netconfig(4) NAME netconfig - network configuration database SYNOPSIS /etc/netconfig DESCRIPTION The network configuration database, /etc/netconfig, is a system file used to store information about networks that are connected to the system. The netconfig database and the routines that access it (see getnetconfig(3N)) are part of the Network Selection component. The Network Selection component also includes getnetpath() routines to provide application-specific network search paths.
netconfig(4) netconfig(4) network_device The network_device is the full pathname of the device used to connect to the transport provider. Typically, this device will be in the /dev directory. The network_device must be specified. translation_libraries The name-to-address translation libraries support a ‘‘directory service’’ (a name-to-address mapping service) for the network. A ‘‘-’’ in this field indicates the absence of any translation_libraries.
netconfig(4) netconfig(4) # gethostbyname, gethostbyaddr, getservbyname, and getservbyport. # There are no nametoaddr_libs for the inet family, and currently # nametoaddr_libs are not supported. # udp tpi_clts v inet udp /dev/udp tcp tpi_cots_ord v inet tcp /dev/tcp AUTHOR netconfig was developed by Sun Microsystems, Inc. FILES /etc/netconfig SEE ALSO getnetconfig(3N), getnetpath(3N), nsswitch.conf(4).
netgroup(4) netgroup(4) NAME netgroup - list of network groups DESCRIPTION File /etc/netgroup defines network-wide groups, and is used for permission checking when executing remote mounts, remote logins, and remote shells. For remote mounts, the information in netgroup classifies machines; for remote logins and remote shells, it classifies users. Each line of the netgroup file defines a group and has the format groupname member1 member2 ... where member i is either another group name, or a triple.
netrc(4) netrc(4) NAME netrc - login information for ftp and rexec DESCRIPTION The .netrc file contains login and initialization information used by the ftp autologin process, by the rexec() library routine, and by the rexec command (see ftp (1), rexec (3N), and remsh (1)), respectively. This file is optional. It exists, if at all, in the user’s home directory. If the .
netrc(4) netrc(4) EXAMPLES The following is a valid entry for the host hpxdzg whose guest account has the password sesame: machine hpxdzg login guest password sesame WARNINGS It is a security risk to have unencrypted passwords in a file. AUTHOR netrc was developed by the University of California, Berkeley. FILES $HOME/.netrc SEE ALSO ftp(1), remsh(1), rexec(3N).
nettlgen.conf(4) nettlgen.conf(4) NAME nettlgen.conf - network tracing/logging and kernel logging configuration file SYNOPSIS /etc/nettlgen.conf DESCRIPTION /etc/nettlgen.conf, the configuration file for Common Network Tracing/Logging and Kernel Logging commands commands, contains configuration information used by the nettl, kl, and netfmt commands (see nettl (1M), kl(1M), and netfmt (1M)).
nettlgen.conf(4) nettlgen.conf(4) If more information is desired than the special terse form used for console logging, turn off console logging and start a formatter with an options file specifying the filters to use (see netfmt (1M)). The Log Port Size defines the number of outstanding messages possible in the log queue. For logging, 256-byte buffers are used. The number chosen here indicates how much space to allocate in kilobytes.
nettlgen.conf(4) 6 nettlgen.conf(4) Write To Disk Flag Set to 1 if writing messages to disk is to be enabled when KL facility is started, 0 if not. The KL Minimum and Maximum Queue Size define the number of outstanding messages possible in the kernel log queue. The default size is 1000. The Maximum Log File Space determines the maximum logging file size to be allowed. Log files are split into two parts.
nettlgen.conf(4) nettlgen.conf(4) range, i.e. subsystems supported by KL facility, should have Subsystem Type to be k. 6 Subformatter Shared Library Name of the shared library file containing the subformatter functions listed below. 7 Subformatter Message Catalog Basename of the message catalog to use when formatting data for this subsystem. 8 Subformatter Function C function in the subformatter library to call when formatting data for this subsystem.
nettlgen.conf(4) nettlgen.conf(4) data is always in the .KLOG0 file. # # KL INFORMATION # KL:1000:1000:1M:/var/adm/kl:0 The following example turns on write to disk option when KL facility is started, decreases the size of the kernel logging queue to 500 messages and increases the size of the log file space to 5M bytes. Other values are the same as the default. # # KL INFORMATION # KL:500:5000:5M:/var/adm/kl:1 The following example shows a typical subsystem record.
networks(4) networks(4) NAME networks - network name data base DESCRIPTION The /etc/networks file associates Internet (IP) addresses with official network names and aliases. This allows the user to refer to a network by a symbolic name instead of using an Internet address. For each network, a single line should be present with the following information: Aliases are other names under which a network is known. For example: loop 192.46.
nisfiles(4) nisfiles(4) NAME nisfiles - NIS+ database files and directory structure SYNOPSIS /var/nis DESCRIPTION The Network Information Service Plus (NIS+) uses a memory-based, replicated database. This database uses a set of files in the /var/nis directory for checkpointing to stable storage and for maintaining a transaction log. Additionally, the NIS+ server and client use files in this directory to store binding and state information.
nisfiles(4) nisfiles(4) deleted. Currently, NIS+ does not automatically do checkpointing. The system administrator may want to do nisping-C (see nisping (1M)) operations periodically (such as, once a day) to checkpoint the log file. This can be done either through a cron (1M) job, or manually. hostname /root_dir On root servers, this file stores the database associated with the root directory. It is similar to other table databases. The corresponding log file is called root_dir.log. hostname /cred.
nlist(4) nlist(4) NAME nlist, nlist64 - nlist/nlist64 structure format SYNOPSIS #include Remarks The exact content of the structure defined below can be best found by examining /usr/include/nlist.h. It varies somewhat between various HP-UX implementations. DESCRIPTION nlist() and nlist64() can be used to extract information from the symbol table in an object file (see nlist (3E)). They are basically the same tool, and both can process SOM and Elf files.
nlspath(4) nlspath(4) NAME nlspath - NLSPATH configuration file DESCRIPTION The file /etc/default/nlspath allows the superuser to restrict the paths set by others through an environment variable NLSPATH to locate message catalogs for setuid or setgid root programs. This file contains only one entry with the following format: NLSPATH=pseudo-pathname :pseudo-pathname :... pseudo-pathnames must be separated by a colon.
nsswitch.conf(4) nsswitch.conf(4) NAME nsswitch.conf - configuration file for the name-service switch SYNOPSIS /etc/nsswitch.conf DESCRIPTION The operating system uses a number of "databases" of information about hosts, users (passwd), groups and so forth. Data for these can come from a variety of sources: host-names and -addresses, for example, may be found in /etc/hosts, NIS, NIS+, LDAP or DNS.
nsswitch.conf(4) nsswitch.conf(4) anywhere in a line, to be used to begin comments. The database and source names are case-sensitive, but action and status names are case-insensitive. The default criteria are to continue on anything except SUCCESS; in other words, [SUCCESS=return NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue].
nsswitch.conf(4) passwd: group: hosts: networks: protocols: rpc: publickey: netgroup: automount: aliases: services: sendmailvars: ipnodes: nsswitch.
nsswitch.conf(4) nsswitch.conf(4) WARNINGS Within each process that uses nsswitch.conf(), the entire file is read only once. If the file is later changed, the process will continue using the old configuration. Programs that use the getXX byYY () functions cannot be linked statically since the implementation of these functions requires dynamic linker functionality to access the shared objects /usr/lib/nss_SSS.sl.1 at run time.
pam.conf(4) pam.conf(4) NAME pam.conf - configuration file for pluggable authentication modules SYNOPSIS /etc/pam.conf DESCRIPTION pam.conf is the configuration file for the Pluggable Authentication Module architecture, or PAM. A PAM module provides functionality for one or more of four possible services: authentication, account management , session management , and password management . An authentication service module provides functionality to authenticate a user and set up user credentials.
pam.conf(4) pam.conf(4) Integrating Multiple Authentication Services With Stacking When a service_name of the same module_type is defined more than once, the service is said to be stacked . Each module referenced in the module_path for that service is then processed in the order that it occurs in the configuration file. The control_flag field specifies the continuation and failure semantics of the modules, and may be required, optional, or sufficient.
pam.conf(4) pam.conf(4) Notes If an error is found in an entry due to invalid service_name , module_type , or control_flag, then the entry is ignored. If there are no valid entries for the given module_type , the PAM framework returns an error to the application. EXAMPLES The following is a sample pam.conf configuration file. Lines that begin with the # symbol are treated as comments, and therefore ignored. # # PAM configuration # # Authentication management for login service is stacked.
pam.conf(4) pam.conf(4) # # Password management passwd password required passwd password required other password required /usr/lib/security/$ISA/libpam_updbe.so.1 /usr/lib/security/$ISA/libpam_unix.so.1 /usr/lib/security/$ISA/libpam_unix.so.1 Utilities and Files A list of utilities that are known to use PAM include: login, passwd, su, and dtlogin. The PAM configuration file does not dictate either the name or the location of the service specific modules.
pam_user.conf(4) pam_user.conf(4) NAME pam_user.conf - users configuration file for pluggable authentication modules SYNOPSIS /etc/pam_user.conf DESCRIPTION pam_user.conf is the user configuration file for the Pluggable Authentication Module architecture, or PAM. It is not designed to replace the PAM system configuration file, pam.conf. For PAM to work properly, pam.conf is mandatory (see pam.conf (4)). pam_user.conf is optional. It is used only when a user basis configuration is needed.
pam_user.conf(4) susan pam_user.conf(4) password /usr/lib/security/$ISA/libpam_unix.so.1 use_psd SEE ALSO pam(3), pam.conf(4).
passwd(4) passwd(4) NAME passwd - password file SYNOPSIS #include DESCRIPTION /etc/passwd contains the following information for each user: • • • • • • • login name encrypted password numerical user ID numerical group ID reserved gecos ID initial working directory program to use as shell This is an ASCII file. Each field within each user’s entry is separated from the next by a colon. Each user is separated from the next by a newline. This file resides in the /etc directory.
passwd(4) passwd(4) The remaining two characters define the week when the password was last changed (a null string is equivalent to zero). M and m have numerical values in the range 0 through 63 that correspond to the 64character set of "digits" shown above. If m = M = 0 (derived from the string . or ..), the user is forced to change his password next time he logs in (and the "age" disappears from his entry in the password file). If m > M (signified, for example, by the string .
passwd(4) passwd(4) WARNINGS The login shell for the root user (uid 0) must be /sbin/sh to guarantee the system can always boot. Other shells such as sh, ksh, and csh are all located under the /usr directory which may not be mounted during earlier stages of the bootup process. Changing the login shell of the root user to a value other than /sbin/sh is allowed but may result in a non-functional system. The information kept in the gecos field may conflict with unsupported or future uses of this field.
passwd(4) passwd(4) /etc/passwd /etc/shadow Standard password file used by HP-UX. Shadow password file. SEE ALSO chfn(1), chsh(1), finger(1), login(1), passwd(1), pwck(1), pwconv(1M), useradd(1M), a64l(3C), crypt(3C), getpass(3C), getpwent(3C), getprpwent(3), authcap(4), shadow(4), limits(5).
pcf(4) pcf(4) NAME pcf - port configuration file used by DDFA software Description A port configuration file is used by the Datacommunications and Terminal Controller Device File Access (DDFA) software to configure individual terminal server ports. The generic name of the template file is pcf. In practice, it is renamed for each port that needs different configuration values and the values are altered appropriately for the device attached to the port.
pcf(4) pcf(4) value effectively leaves the connection permanently open. status_request: This can have the value disable or enable. When it is enabled, the software sends a status request to the device attached to the terminal server and processes the reply as follows: LP_OK (0x30) ocd continues processing. LP_NO_PAPER (0x31) ocd retries within the limits of the status timer. LP_BUSY (0x32) ocd retries within the limits of the status timer.
pcf(4) pcf(4) SEE ALSO dpp(1M), ocd(1M), ocdebug(1M), dp(4), ddfa(7).
pfs(4) pfs(4) NAME pfs, PFS - portable file system DESCRIPTION The Portable File System, or PFS, allows access to a variety of CD-ROM file systems. Currently supported file systems include: iso9660, high sierra, RockRidge Interchange. The PFS package consists of 7 programs: pfs_mountd is responsible for maintaining local and remote mounts. It must be running on both PFS clients and PFS servers. The pfs_mountd program validates arguments, and spawns pfs_mountd.rpc. pfs_mountd.
ppp.Auth(4) ppp.Auth(4) NAME ppp.Auth - PPP authentication file format DESCRIPTION The file /etc/ppp/Auth contains values used by HP PPP’s implementation of the link-level authentication protocols, CHAP (Challenge Handshake Authentication Protocol) and PAP (Password Authentication Protocol). This implementation of both CHAP and PAP conforms to RFC 1334, PPP Authentication Protocols. CHAP is a stronger authentication mechanism and should be used whenever possible, in preference over PAP.
ppp.Auth(4) ppp.Auth(4) AUTHOR ppp.Auth was developed by the Progressive Systems. SEE ALSO ppp.Devices(4), ppp.Dialers(4), ppp.Filter(4), ppp.Keys(4), ppp.Systems(4), services(4), pppd(1), RFC 792, RFC 1548, RFC 1332, RFC 1334.
ppp.Devices(4) ppp.Devices(4) NAME ppp.Devices - PPP physical device description file format DESCRIPTION The file /etc/ppp/Devices associates dialer types with physical devices and speeds. pppd examines it when placing a call to a neighboring machine. If no suitable speed is found, or if all devices associated with that speed are busy, pppd will try again later. Format Entries are one to a line; blank lines are ignored. Comments begin with a ‘#’ and extend to the end of the line.
ppp.Devices(4) ppp.Devices(4) EXAMPLE # # Devices - PPP devices file # #Dialer device speed Optional parameters T2500-PEP cua 19200-PEP rtscts T1600 cub 38400 rtscts Direct rsd0a/0 1536000 internal-clocking Oddball rsd0a/1 64000 cua 9600 5551212 In the last line of this example, the 64Kb synchronous modem on the SnapLink’s port 1 has an asynchronous dialer interface attached to the workstation’s port ‘a’.
ppp.Dialers(4) ppp.Dialers(4) NAME ppp.Dialers - PPP dialer description file format DESCRIPTION The file /etc/ppp/Dialers describes how to dial each type of modem attached to the UNIX system that is to be made available for outbound PPP calls. pppd examines it when placing a call to a neighboring machine. When pppd selects a line from Systems, it uses the ‘speed’ field to select an entry in Devices, from which it uses the ‘dialer’ field to select an entry in Dialers.
ppp.Dialers(4) A pA ppp.Dialers(4) \ddd Send or receive a character, specified in octal digits. \p Pause for .25 second before proceeding (send only). \d Delay for two seconds before proceeding (send only). \K Send a break (.25 second of zero bits). \M Disable hangups (sets CLOCAL or LNOHANG). \m enable hangups (unsets CLOCAL or LNOHANG) (the default). \c Don’t append a carriage return character after sending the preceding string (send only). \q Don’t print succeeding send strings (e.g.
ppp.Filter(4) ppp.Filter(4) NAME ppp.Filter - PPP packet filter specification file format DESCRIPTION The file /etc/ppp/Filter describes how on-demand PPP links are to be managed. By default, any type of packet causes the link (if down) to be brought up (connected to its remote end); any packet is allowed to traverse the link; and any packet is sufficient to reset the idle timer, expiration of which would cause the link to be shut down.
ppp.Filter(4) ppp.Filter(4) In the ‘log’ filter specification, the special keyword ‘trace’ causes the contents (as well as headers) of the indicated type of packet to be written to the log file. Also in the ‘log’ filter specification, the special flag ‘rejected’ signifies that the packet is to be logged only if it was rejected by the ‘pass’ filter.
ppp.Filter(4) default ppp.Filter(4) bringup all pass all keepup all log !all The default behavior is no restriction of packets, and no logging. Internet Firewall A ‘pass’ line like this might be appropriate as a security firewall between an organizational network and the larger Internet: internet-gateway bringup !ntp !3/icmp !5/icmp !11/icmp !who !route !nntp !89 pass nntp/137.39.1.2 !nntp telnet/syn/recv/137.175.0.
ppp.Filter(4) ppp.Filter(4) # # Filter PPP configuration file binding packet # types to actions. # # For packets that would pass, these services # will bring up the link: # backbone bringup smtp nntp domain telnet ftp # # Once brought up, these will pass (or not): # pass !131.119.250.104 domain/137.175.42.0/255.255.255.0 !137.175.42.
ppp.Filter(4) ppp.Filter(4) (‘ftp-data’) rather than the socket/protocol notation. If your /etc/services file is missing some application-level protocols that you consider useful, you can populate it with entries from the Assigned Numbers RFC, number 1340.
ppp.Keys(4) ppp.Keys(4) NAME ppp.Keys - PPP encryption keys file format RESTRICTIONS Encryption is not available in software exported from the USA. The HP’s pppd command does not support gw-crypt option, customer may contact sales@progressive-systems.com to obtain encryption functionality. DESCRIPTION The keys file named in the gw-crypt option on the pppd command line contains key values used by HP PPP’s implementation of link-level encryption.
ppp.Keys(4) ppp.Keys(4) 003C00F001C007 1E007800E00380 E1FF87FF1FFC7F FFC3FF0FFE3FF8 SECURITY CONCERNS The keys file should be mode 600 or 400, and owned by root. Packets’ IP headers are not encrypted, though their TCP, UDP, or ICMP headers are encrypted along with the user data portion. This allows encrypted packets to traverse normal internetworks, but permits snoopers to analyze traffic by its endpoints.
ppp.Systems(4) ppp.Systems(4) NAME ppp.Systems - PPP neighboring systems description file format DESCRIPTION The file /etc/ppp/Systems describes how to connect with neighboring systems via PPP. Format Entries are one to a line; blank lines are ignored. Comments begin with a ‘#’ and extend to the end of the line. Upper/lower case distinctions are ignored in hostname specifications, but are significant elsewhere. Fields on a line are separated by horizontal white space (blanks or tabs).
ppp.Systems(4) ppp.Systems(4) ignored, but must be present as a place-holder. phone number The value to replace the \T escape sequence in the dialer script. If the device field names an entry in /dev, the phone number field is optional. If the device field is ‘tcp...’ or ‘telnet...’, the phone number field is ignored if present, but must be present as a placeholder. chat script A description of the conversation that pppd holds with the remote machine.
ppp.Systems(4) ppp.Systems(4) \q Don’t print following send strings (e.g. a password) in any debugging or logging output. Subsequent \q sequences toggle ‘quiet’ mode. \A Parse the incoming string as an IP address, written as four decimal numbers separated by periods, and use it for the local end of the point-to-point connection (receive only). EXAMPLE In the example below, we call host ‘everyone’ using a Telebit PEP modem with its DTE interface set at 19200 bps. We call host ‘nobody’ using a V.32/V.
privgrp(4) privgrp(4) NAME privgrp - format of privileged values SYNOPSIS #include DESCRIPTION setprivgrp() sets a mask of privileges, and getprivgrp (2) returns an array of structures giving privileged group assignments on a per-group-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.
privgrp(4) privgrp(4) SEE ALSO getprivgrp(1), setprivgrp(1M), chown(2), getprivgrp(2), lockf(2), plock(2), rtprio(2), rtsched(2), serialize(2), setgid(2), setuid(2), shmctl(2), mpctl(2), pset_create(2).
profile(4) profile(4) NAME profile - set up user’s environment at login time DESCRIPTION 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. .
proto(4) proto(4) NAME proto - prototype job file for at(1) SYNOPSIS /var/adm/cron/.proto /var/adm/cron/.proto. queue DESCRIPTION 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. 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.
protocols(4) protocols(4) NAME protocols - protocol name data base DESCRIPTION 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 .
prpwd(4) prpwd(4) NAME prpwd - protected password authentication database files used for trusted systems SYNOPSIS /tcb/files/auth/... DESCRIPTION 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.
prpwd(4) u_succhg prpwd(4) This field is a time_t value that indicates the time of the last successful password change. This field should only be set by programs that can be used to change the account password. u_unsucchg This field is a time_t value that indicates the time of the last unsuccessful password change. This field should only be set by programs that can be used to change the account password. u_acct_expire This field is the time_t time is seconds that the account will be usable.
prpwd(4) prpwd(4) u_numunsuclog This field contains a count of the number of unsuccessful login attempts to the account. This field is reset when a successful login to the account occurs. u_unsuctty This field is a character string that identifies the name of the terminal or remote host associated with the last unsuccessful login attempt to the account.
publickey(4) publickey(4) NAME publickey - public key database SYNOPSIS etc/publickey DESCRIPTION /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.
queuedefs(4) queuedefs(4) NAME queuedefs - queue description file for at, batch, and crontab SYNOPSIS /var/adm/cron/queuedefs DESCRIPTION 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.
rc.config(4) rc.config(4) NAME rc.config, rc.config.d - files containing system configuration information SYNOPSIS /etc/rc.config /etc/rc.config.d/* /etc/TIMEZONE DESCRIPTION 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.
rc.config(4) rc.config(4) SEE ALSO rc(1M).
rcsfile(4) rcsfile(4) NAME rcsfile - format of RCS files DESCRIPTION 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 phrases.
rcsfile(4) rcsfile(4) the first 2(n-1) number fields of the deltas on that sequence is called the branchpoint. The branches field of a node contains a list of the numbers of the first nodes of all sequences for which it is a branchpoint. This list is ordered in increasing numbers. EXAMPLES A rA head | | v --------/ \ / \ | | / \ / \ / \ / \ | 2.1 | / \ / \ / \ / \ | | / \ __/ \__ /1.2.1.3\ /1.3.1.1\ | | /1.2.2.2\ /1.2.2.1.1.
resolver(4) resolver(4) NAME resolver - resolver configuration file SYNOPSIS /etc/resolv.conf DESCRIPTION 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(4) domains are not local, and that queries time out if no server is available for one of the domains. The search list is currently limited to six domains with a total of 256 characters. The first domain in the search list must be the local domain for short names to work properly in various files (such as .rhosts and inetd.sec) sortlist Causes addresses returned by gethostbyname(3N) to be sorted in accordance with network numbers specified in the address list.
resolver(4) resolver(4) 1535, located in /usr/share/doc. AUTHOR resolver was developed by the University of California, Berkeley. FILES /etc/resolv.conf Resolver configuration file.
rmtab(4) rmtab(4) NAME rmtab - local file system mount statistics DESCRIPTION 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.conf(4) NAME rndc.conf - rndc configuration file DESCRIPTION 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.
rndc.conf(4) rndc.conf(4) The secret can be generated using dnssec-keygen as follows: $ dnssec-keygen -a hmac-md5 -b 128 -n user rndc The base-64 string will appear in two files, Krndc.+157.+ {random }.key and Krndc.+157.+ {random }.private . After extracting the key to be placed in the rndc.conf and named.conf key statements, the .key and .private files can be removed. NAME SERVER CONFIGURATION The name server must be configured to accept rndc connections and to recognize the key specified in the rndc.
rpc(4) rpc(4) NAME rpc - rpc program number data base SYNOPSIS /etc/rpc DESCRIPTION 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. EXAMPLES Here is an example of an /etc/rpc file: # # rpc 12.
sccsfile(4) sccsfile(4) NAME sccsfile - format of SCCS file DESCRIPTION An SCCS file is an ASCII file consisting of six logical parts: checksum delta table user names flags body Sum of all characters in the file except the first line. Contains information about each delta. Login names and/or numerical group IDs of users who are allowed to add deltas. Definitions of internal keywords. comments Arbitrary descriptive information about the file. Actual text lines intermixed with control lines.
sccsfile(4) Flags sccsfile(4) Keywords used internally (see admin (1) for more information on their use).
sccsfile(4) sccsfile(4) Type Represented By: insert delete end @I DDDDD @D DDDDD @E DDDDD The digit string is the serial number corresponding to the delta for the control line. WARNINGS SCCS files can be any length, but the number of lines in the text file itself cannot exceed 99 999 lines. SEE ALSO admin(1), delta(1), get(1), prs(1).
securenets(4) securenets(4) NAME securenet - NIS map security file DESCRIPTION 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 it exists.
security(4) security(4) NAME security - security defaults configuration file DESCRIPTION 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.
security(4) security(4) NOLOGIN=0 Ignore the /etc/nologin file and do not exit if the /etc/nologin file exists. NOLOGIN=1 Display the contents of the /etc/nologin file and exit if the /etc/nologin file exists. Default value: NOLOGIN=0 NUMBER_OF_LOGINS_ALLOWED This parameter controls the number of simultaneous logins allowed per user.
security(4) security(4) PASSWORD_MAXDAYS=N A new password is valid for up to N days, after which the password must be changed. Default value: PASSWORD_MAXDAYS=-1 password aging is turned off. PASSWORD_MINDAYS This parameter controls the default minimum number of days before a password can be changed. This value is used by the authentication subsystem during the password change process in the case where aging restrictions do not already exist for the user.
security(4) security(4) UMASK=default_umask The umask is set or restricted further with the value of default_umask. Default value: UMASK=0 Notes Use the functions defined in secdef (3) to read the values of the parameters defined in this file. AUTHOR The security file was developed by HP. FILES /etc/default/security SEE ALSO login(1), passwd(1), su(1), init(1M), secdef(3), pam_unix(5).
services(4) services(4) NAME services - service name data base DESCRIPTION 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 than 1023.
services.window(4) services.window(4) NAME services.window - file containing applications and their associated memory window id DESCRIPTION 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 .
shadow(4) shadow(4) NAME shadow - shadow password file SYNOPSIS #include DESCRIPTION The /etc/shadow file is created from the /etc/passwd file by the pwconv command. It is readable only by a privileged user. It can be modified by the passwd, useradd, usermod, and userdel commands. Programs may use the interfaces described in the getspent (3C) manpage to access this information. These functions return a pointer to an spwd structure, which is defined in the header file.
shells(4) shells(4) NAME shells - list of allowed login shells SYNOPSIS /etc/shells DESCRIPTION /etc/shells is an ASCII file containing a list of legal shells on the system. Each shell is listed in the file by its absolute path name. Lines or portions of lines beginning with # are assumed to be comments and are ignored. Blank lines are also ignored. AUTHOR shells was developed by HP and the University of California, Berkeley. FILES /etc/shells SEE ALSO chsh(1), ftpd(1M), getusershell(3C).
slp.conf(4) slp.conf(4) NAME slp.conf - Configuration file for SLP Agents SYNOPSIS /etc/slp.conf DESCRIPTION The /etc/slp.conf file contains various configuration options for the agents which include the clients that use SLP APIs, the Service Agent server and Directory agents. It determines the configuration of all the SLP agents running on that host. The SLP SA server and DA read the slp.conf file during their invocation and also when they are reconfigured by sending the SIGHUP signal.
slp.conf(4) slp.conf(4) UA Configuration The following sections of configuration properties are specified in RFC2614 and are supported for the above categories. DA configuration The configuration properties for DAs are explained in this section. net.slp.isDA A boolean indicating if the SLP server is to act as a DA. If false, slpd runs as SA server. Default is false. net.slp.DAHeartBeat A 32 bit integer giving the number of seconds for the DA heartbeat. The default is 3 hours (10800 seconds).
slp.conf(4) slp.conf(4) net.slp.traceDrop A boolean controlling printing of details when a SLP message is dropped for any reason. Default is false. net.slp.traceReg A boolean controlling dumps of all registered services upon registration and deregistration. If true, the contents of the DA or SA server are dumped after a registration or deregistration occurs. Default is false. Network Configuration Properties The properties in this section allow various network configuration properties to be set. net.
slp.conf(4) slp.conf(4) net.slp.SAAttributes A comma-separated list of parenthesized attribute/value list pairs that the SA must advertise in SAAdverts. The property must be in the SLP attribute list wire format, including escapes for reserved characters. Currently this property is ignored. UA Configuration This section describes configuration properties for the UA. These properties can be set either programmatically by the UA or in the configuration file. net.slp.
slp.reg(4) slp.reg(4) NAME slp.reg - SLP static registration file SYNOPSIS /etc/slp.reg DESCRIPTION The /etc/slp.reg file provides a mechanism for old applications which are not SLP enabled and cannot be converted, and for portably exchanging registrations between SLP implementations. This file contains a list of service registrations that are read by slpd at startup time and advertised later by slpd which can be acting either as the service agent server or the directory agent.
slp.reg(4) slp.reg(4) If the scope list contains scopes that are not in the net.slp.useScopes property (provided that property is set) or are not specified by DHCP, the API library should reject the registration and issue a warning message. AUTHOR slp.reg was developed by the Caldera Systems, Inc. SEE ALSO slpd(1M), libslp(3N), slp.conf(4), slp_syntax(7). RFC 2614, RFC 2608.
sm(4) sm(4) NAME sm, sm.bak, state - statd directory and file structures SYNOPSIS /var/statmon/sm /var/statmon/sm.bak /var/statmon/state DESCRIPTION /var/statmon/sm and /var/statmon/sm.bak are directories generated by statd (see statd (1M)). Each file in /var/statmon/sm represents one or more machines to be monitored by the statd daemon. Each file in /var/statmon/sm.bak represents one or more machines to be notified by the statd daemon upon its recovery.
snmpd.conf(4) snmpd.conf(4) NAME snmpd.conf - configuration file for the SNMP agent DESCRIPTION When invoked, the SNMP agent reads its configuration information from the /etc/SnmpAgent.d/snmpd.conf configuration file. The SNMP agent is either the snmpd(1M) (included with HP-UX) or the snmpd.ea (purchased with the HP OpenView product). The SNMP agent will not be able to reply if no values are configured in /etc/SnmpAgent.d/snmpd.conf, i.e., /etc/SnmpAgent.d/snmpd.conf is empty.
snmpd.conf(4) snmpd.conf(4) usmUserEngineID is an OctetString, which is authoritative SNMP engine’s administratively unique identifier. For snmpget/snmpset requests, the value in agent configuration file will be localSNMPID . usmUserName is user name in ASCII text. usmUserAuthProtocol is the Authentication Protocol used for sending and receiving messages, on behalf of this SNMP engine. Currently supported values are usmNoAuthProtocol and usmHMACMD5AuthProtocol.
snmpd.conf(4) vacmAccessStorageType snmpd.conf(4) is nonVolatile, permanent, or readOnly. When the TAG is vacmViewTreeFamilyEntry, the format of the VALUE clause is as follows: vacmViewTreeFamilyViewName vacmViewTreeFamilySubtree vacmViewTreeFamilyMask vacmViewTreeFamilyType vacmViewTreeFamilyStorageType where: vacmViewTreeFamilyViewName is the name of the family of this view of subtrees. vacmViewTreeFamilySubtree is the object Identifier that defines the subtree.
snmpd.conf(4) snmpTargetAddrMMS snmpd.conf(4) is Maximum Message Size that can be transmitted between local host and host with address snmpTargetAddrTAddress without fragmentation. Default size is 2048. When the TAG is snmpNotifyEntry, the format of the VALUE clause is as follows: snmpNotifyName snmpNotifyTag snmpNotifyType snmpNotifyStorageType where: snmpNotifyName is the ASCII text representing the name of notification.
snmpd.conf(4) snmpd.conf(4) location: 1st Floor near Mens Room # Specify Bob Jones is responsible for this agent # and his phone number is 555-2000 contact: Bob Jones (Phone 555-2000) # Create a SNMPv3 user ’v3usr’ with No Authentication Protocol. usmUserEntry localSnmpID v3usr usmNoAuthProtocol 1.3.6.1.6.3.10.1.2.1 \ nonVolatile whereValidRequestsOriginate # Create a SNMPv3 user ’v3usr’ with Authentication enabled and # password as "passwd". usmUserEntry localSnmpID v3usr usmHMACMD5AuthProtocol 1.3.6.1.
softkeys(4) softkeys(4) NAME softkeys - keysh softkey file format BACKGROUND keysh softkey information is stored in the form of a softkey node hierarchy. The top level of this hierarchy represents the softkey commands themselves; lower levels represent various command options and parameters. The softkey labels form a window into this softkey node hierarchy through which the user can view and select eligible nodes.
softkeys(4) softkeys(4) Each softkey node can have the following optional attribute fields: disable count Selecting this node will disable count softkey nodes to the right of this one - default is 0. enable count Selecting this softkey will enable count softkey nodes to the right of this one - default is 0. {filtercommand} This node is only active for filters or commands, respectively - default is either.
softkeys(4) softkeys(4) An edit statement is: • • • an expression followed by a ;, an if statement, or a word allocation statement.
softkeys(4) word[number ]=string word[number ]+=number word[number ]-=number word[number ]*=number word[number ]/=number word[number ]%=number word[number 1]&=string softkeys(4) simple assignment add and assign subtract and assign multiply and assign divide and assign modulus and assign concatenate and assign if Statement The if statement is similar to the full-block mode if statement in awk, and is structured as follows: if(number ) { edit statement . . . } else { edit statement . . .
softkeys(4) softkeys(4) .IL tag indent Begin a new indented line (similar to .IP except no blank line is displayed). Note that these macros are recognized anywhere in the input helptext, not just at the beginning of a line. Also, all macro arguments must be present , even if they consist of nothing more than a quoted empty string.
symlink(4) symlink(4) NAME symlink - symbolic link DESCRIPTION A symbolic (or soft ) link is a file whose name indirectly refers (points) to a relative or absolute path name. During path name interpretation, a symbolic link to a relative path name is expanded to the path name being interpreted, and a symbolic link to an absolute path name is replaced with the path name being interpreted. Thus, given the path name /a/b/c/d: If c is a symbolic link to a relative path name such as ..
system(4) system(4) NAME system - system description configuration files DESCRIPTION The HP-UX system description file describes kernel configuration information used by the kconfig(1M) and mk_kernel (1M) commands. The system description file consists of the following information: • A line specifying the version of the system file. • The list of packaged and traditional kernel modules to be configured. • Planned values for system tunable parameters, and other system-wide configuration information.
system(4) system(4) selects the driver for SCSI disk drives. module pseudodrv loaded 0.1.0 dynamically loads the module pseudodrv. System files may also contain lines that are used to: • • • • define the swap device define the dump device(s) provide an explicit binding a driver to a hardware path define status and values of selected system parameters. Lines are constructed as indicated below for each category. • Swap Device Specification No more than one swap specification is allowed.
system(4) system(4) One or more driver to hardware path specifications is allowed. If a driver statement is provided, the specified software module is forced into the kernel I/O system at the given hardware path. This can be used to make the system recognize a device that could not be recognized automatically. driver hw_path driver_name Bind the driver into the kernel I/O system at the given hardware path.
tar(4) tar(4) NAME tar - format of tar tape archive DESCRIPTION The header structure produced by tar (see tar (1)) is as follows (the array size defined by the constants is shown on the right): struct { char char char char char char char char char char char char char char char char } dbuf; name[NAMSIZ]; (100) mode[MODE_SZ]; (8) uid[UID_SZ]; (8) gid[GID_SZ]; (8) size[SIZE_SZ]; (12) mtime[MTIME_SZ]; (12) chksum[CHKSUM_SZ]; (8) typeflag; linkname[NAMSIZ]; (100) magic[MAGIC_SZ]; (6) version[VERSION_SZ]; (2)
tcpd.conf(4) tcpd.conf(4) NAME tcpd.conf - configuration file for tcpd DESCRIPTION When inetd invokes tcpd for a service, it will read /etc/tcpd.conf and perform access control checks (see tcpd (1M)). Each line in the file is treated either as a comment or as configuration information. Commented lines begin with #. Uncommented lines contain two required fields, key and value. The fields are separated by tabs and/or spaces. A line can be continued if it terminates with a backslash (\).
tcpd.conf(4) tcpd.conf(4) To make tcpd to allow a host on reverse lookup failure and process that host as PARANOID, in ACLs: on_reverselookup_fail allow To set the extended logging option: log_level extended AUTHOR tcpd.conf was developed by the Hewlett-Packard. SEE ALSO inetd(1M), tcpd(1M).
term(4) term(4) NAME term - format of compiled term file SYNOPSIS term DESCRIPTION Compiled terminfo descriptions are placed under the directory /usr/share/lib/terminfo. In order to avoid a linear search of a huge HP-UX 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, hp110 can be found in the file /usr/share/lib/terminfo/h/hp110.
term(4) term(4) 110|hp110|hp110a portable computer, am, xhp, da, db, mir, cols#80, lines#16, lm#0, cbt=\Ei, bel=ˆG, cr=\r, tbc=\E3, clear=\E&a0y0C\EJ, el=\EK, ed=\EJ, hpa=\E&a%p1%dC, cup=\E&a%p1%dy%p2%dC, cud1=\EB, cub1=\b, cuf1=\EC, cuu1=\EA, cvvis=\E&j@, dch1=\EP, dl1=\EM, smir=\EQ, smso=\E&dB, sgr0=\E&d@, rmir=\ER, rmso=\E&d@, is2=\E&j@, if=/usr/share/lib/tabset/stdcrt, il1=\EL, kbs=\b, kcud1=\EB, khome=\Eh, kcub1=\ED, kcuf1=\EC, kcuu1=\EA, rmkx=\E&s0A, smkx=\E&s1A, vpa=\E&a%p1%dY, ind=\n, hts=\E1, ht=
terminfo(4) terminfo(4) (ENHANCED CURSES) NAME terminfo - printer, terminal, and modem capability database SYNOPSIS /usr/lib/terminfo/?/* DESCRIPTION The requirements in this manpage are in effect only for implementations that claim Enhanced Curses compliance.
terminfo(4) terminfo(4) (ENHANCED CURSES) alias1 | alias2 | ... | aliasn | longname, whitespace am, lines #24, whitespace home=\Eeh, The first line, commonly referred to as the header line, must begin in column one and must contain at least two aliases separated by vertical bars. The last field in the header line must be the long name of the device and it may contain any string.
terminfo(4) terminfo(4) (ENHANCED CURSES) rest_of_feature_line : features COMMA NEWLINE | COMMA NEWLINE ; features : COMMA feature | features COMMA feature ; aliases : PIPE ALIAS | aliases PIPE ALIAS ; feature : BOOLEAN | NUMERIC | STRING ; (1) An ALIAS that begins in column one. This is handled by the lexical analyzer. (2) A BOOLEAN feature that begins after column one but is the first feature on the feature line. This is handled by the lexical analyzer.
terminfo(4) terminfo(4) (ENHANCED CURSES) tgetent() (in the cases where the following table lists a Termcap code) and tigetflag() (see tgetent (3X) and tigetflag(3X)). The table of capabilities has the following columns: Variable Names for use by the Curses functions that operate on the terminfo database. These names are reserved and the application must not define them. Capname The short name for a capability specified in the terminfo source file.
terminfo(4) terminfo(4) (ENHANCED CURSES) Numbers A Variable bit_image_entwining bit_image_type buffer_capacity buttons columns dot_horz_spacing dot_vert_spacing init_tabs label_height label_width lines lines_of_memory Capname bitwin bitype bufsz btns cols spinh spinv it lh lw lines lm Termcap Yo Yp Ya BT co Yc Yb it lh lw li lm max_attributes ma ma magic_cookie_glitch max_colors max_micro_address max_micro_jump max_pairs maximum_windows micro_col_size micro_line_size no_color_video num_labels num
terminfo(4) terminfo(4) (ENHANCED CURSES) Strings Variable acs_chars alt_scancode_esc Capname acsc scesa Termcap ac S8 back_tab bell bit_image_carriage_return bit_image_newline bit_image_repeat carriage_return change_char_pitch change_line_pitch change_res_horz change_res_vert change_scroll_region char_padding char_set_names clear_all_tabs clear_margins cbt bel bicr binel birep cr cpi lpi chr cvr csr rmp csnm tbc mgc bt bl Yv Zz Xy cr ZA ZB ZC ZD cs rP Zy ct MC clear_screen clr_bol clr_eol clr_eos c
terminfo(4) terminfo(4) (ENHANCED CURSES) A tA enter_am_mode enter_blink_mode enter_bold_mode enter_ca_mode enter_delete_mode enter_dim_mode enter_doublewide_mode enter_draft_quality enter_horizontal_hl_mode enter_insert_mode enter_italics_mode enter_left_hl_mode enter_leftward_mode enter_low_hl_mode enter_micro_mode enter_near_letter_quality enter_normal_quality enter_pc_charset_mode enter_protected_mode enter_reverse_mode enter_right_hl_mode enter_scancode_mode enter_secure_mode enter_shadow_mode ente
terminfo(4) terminfo(4) (ENHANCED CURSES) from_status_line goto_window hangup init_1string init_2string init_3string init_file init_prog initialize_color initialize_pair insert_character insert_line insert_padding fsl wingo hup is1 is2 is3 if iprog initc initp ich1 il1 ip fs WG HU i1 is i3 if iP IC Ip ic al ip Return from status line Go to window #1 Hang-up phone Terminal or printer initialization string Terminal or printer initialization string Terminal or printer initialization string Name of initial
terminfo(4) terminfo(4) (ENHANCED CURSES) A tA key_message key_mouse key_move key_next key_npage key_open key_options key_ppage key_previous key_print key_redo key_reference key_refresh key_replace key_restart key_resume key_right key_save key_sbeg key_scancel key_scommand key_scopy key_screate key_sdc key_sdl key_select key_send key_seol key_sexit key_sf key_sfind key_shelp key_shome key_sic key_sleft key_smessage key_smove key_snext key_soptions key_sprevious key_sprint key_sr key_sredo key_sreplace k
terminfo(4) terminfo(4) (ENHANCED CURSES) lab_f3 lab_f4 lab_f5 lab_f6 lab_f7 lab_f8 lab_f9 lab_f10 label_format label_off label_on memory_lock memory_unlock meta_off meta_on micro_column_address micro_down micro_left micro_right micro_row_address micro_up mouse_info newline order_of_pins orig_colors orig_pair pad_char parm_dch parm_delete_line parm_down_cursor parm_down_micro parm_ich parm_index parm_insert_line parm_left_cursor parm_left_micro parm_right_cursor parm_right_micro parm_rindex parm_up_cursor
terminfo(4) terminfo(4) (ENHANCED CURSES) A tA reset_1string reset_2string reset_3string reset_file restore_cursor row_address save_cursor scancode_escape scroll_forward scroll_reverse select_char_set set0_des_seq set1_des_seq set2_des_seq set3_des_seq set_a_attributes set_a_background set_a_foreground set_attributes set_background set_bottom_margin set_bottom_margin_parm rs1 rs2 rs3 rf rc vpa sc scesc ind ri scs s0ds s1ds s2ds s3ds sgr1 setab setaf sgr setb smgb smgbp AB AF sa Sb Zk Zl set_clock set
terminfo(4) terminfo(4) (ENHANCED CURSES) user9 underline_char up_half_line wait_tone xoff_character xon_character zero_motion u9 uc hu wait xoffc xonc zerom u9 uc hu WA XF XN Zx User string 9 Underscore one char and move past it Half-line up (reverse 1/2 linefeed) Wait for dial tone XOFF character XON character No motion for the subsequent character Sample Entry The following entry describes the AT&T 610 terminal.
terminfo(4) terminfo(4) (ENHANCED CURSES) Values for numeric capabilities may be specified in decimal, octal or hexadecimal, using normal Clanguage conventions. String Capabilities String-valued capabilities such as el (clear to end of line sequence) are listed by the Capname, an "=", and a string ended by the next occurrence of a comma. A delay in milliseconds may appear anywhere in such a capability, preceded by "$" and enclosed in angle brackets, as in el=\EK$<3> .
terminfo(4) terminfo(4) (ENHANCED CURSES) uses the XON/XOFF flow-control protocol, specify xon. If there is a way to move the cursor one position to the left (such as backspace), that capability should be given as cub1. Similarly, sequences to move to the right, up, and down should be given as cuf1, cuu1, and cud1, respectively. These local cursor motions must not alter the text they pass over; for example, you would not normally use "cuf1=\s" because the space would erase the character moved over.
terminfo(4) terminfo(4) (ENHANCED CURSES) %g[a-z] Get dynamic variable [a-z] and push it. %P[A-Z] Set static variable [a-z] to pop(). %g[A-Z] Get static variable [a-z] and push it. %’c’ Push char constant c. %{nn} Push decimal constant nn. %l Push strlen(pop()).
terminfo(4) terminfo(4) (ENHANCED CURSES) these can be given as cud, cub, cuf, and cuu with a single argument indicating how many spaces to move. These are primarily useful if the device does not have cup, such as the Tektronix 4025. If the device needs to be in a special mode when running a program that uses these capabilities, the codes to enter and exit this mode can be given as smcup and rmcup. This arises, for example, from terminals, such as the Concept, with more than one page of memory.
terminfo(4) terminfo(4) (ENHANCED CURSES) single attribute. terminfo can describe both terminals that have an insert mode and terminals which send a simple sequence to open a blank position on the current line. Give as smir the sequence to get into insert mode. Give as rmir the sequence to leave insert mode. Now give as ich1 any sequence needed to be sent just before sending the character to be inserted.
terminfo(4) terminfo(4) (ENHANCED CURSES) mode, is present. If the terminal has a way of flashing the screen to indicate an error quietly (a bell replacement), then this can be given as flash; it must not move the cursor. A good flash can be done by changing the screen into reverse video, pad for 200 ms, then return the screen to normal video.
terminfo(4) terminfo(4) (ENHANCED CURSES) Sequence \E[0 ;3 ;4 ;5 ;7 ;8 m ^N or ˆO When to Output always if p2 or p6 if p1 or p3 or p6 if p4 if p1 or p5 if p7 always if p9, ˆN; else ˆO terminfo Translation \E[0 %?%p2%p6%|%t;3%; %?%p1%p3%|%p6%|%t;4%; %?%p4%t;5%; %?%p1%p5%|%t;7%; %?%p7%t;8%; m %?%p9%tˆN%eˆO%; Putting this all together into the sgr sequence gives: sgr=\E[0%?%p2%p6%|%t;3%;%?%p1%p3%|%p6% |%t;4%;%?%p5%t;5%;%?%p1%p5% |%t;7%;%?%p7%t;8%;m%?%p9%tˆN%eˆO%;, Remember that sgr and sgr0 must always be
terminfo(4) terminfo(4) (ENHANCED CURSES) smgr; set the tabs using tbc and hts; print the file if; and finally output is3. This is usually done using the init option of tput. Most initialization is done with is2. Special device modes can be set up without duplicating strings by putting the common sequences in is2 and special cases in is1 and is3. Sequences that do a reset from a totally unknown state can be given as rs1, rs2, rf, and rs3, analogous to is1, is2, is3, and if.
terminfo(4) terminfo(4) (ENHANCED CURSES) Line Graphics If the device has a line drawing alternate character set, the mapping of glyph to character would be given in acsc. The definition of this string is based on the alternate character set used in the Digital VT100 terminal, extended slightly with some characters from the AT&T 4410v1 terminal.
terminfo(4) terminfo(4) (ENHANCED CURSES) The numeric variables colors and pairs define the number of colors and color-pairs that can be displayed on the screen at the same time. If a terminal can change the definition of a color (for example, the Tektronix 4100 and 4200 series terminals), this should be specified with ccc (can change color). To change the definition of a color (Tektronix 4200 method), use initc (initialize color).
terminfo(4) terminfo(4) (ENHANCED CURSES) Miscellaneous If the terminal requires other than a null (zero) character as a pad, then this can be given as pad. Only the first character of the pad string is used. If the terminal does not have a pad character, specify npc. If the terminal can move up or down half a line, this can be indicated with hu (half-line up) and hd (half-line down). This is primarily useful for superscripts and subscripts on hardcopy terminals.
terminfo(4) terminfo(4) (ENHANCED CURSES) If el is required to get rid of standout (instead of writing normal text on top of it), xhp should be given. Those Teleray terminals whose tabs turn all characters moved over to blanks, should indicate xt (destructive tabs). This capability is also taken to mean that it is not possible to position the cursor on top of a "magic cookie". Therefore, to erase standout mode, it is necessary, instead, to use delete and insert line.
terminfo(4) terminfo(4) (ENHANCED CURSES) Specifying Printer Resolution The printing resolution of a printer is given in several ways.
terminfo(4) terminfo(4) (ENHANCED CURSES) Effects of Changing the Character/Line Pitches Before After Using cpi with cpix clear: orhi’ orc’ Using cpi with cpix set: orhi orc = orhi / Vcpi orhi’ orc’ Using lpi with lpix clear: orhi = orc * Vcpi orc orvi’ orl’ Using lpi with lpix set: orvi orl = orvi / Vlpi orvi’ orl’ Using chr: orvi = orl * Vlp orl orhi’ orc’ Using cvr: orhi Vchr orvi’ orl’ Using cpi or chr: orvi Vcvr widcs’ mcs’ widcs = widcs’ * orc / orc’ mcs = mcs’ * orc / orc’ Vchr, Vcpi,
terminfo(4) terminfo(4) (ENHANCED CURSES) Limits to Motion mjump Limit on use of mcub1, mcuf1, mcuu1, mcud1 maddr Limit on use of mhpa, mvpa xhpa xvpa If set, hpa and mhpa can’t move left If set, vpa and mvpa can’t move up If a printer needs to be in a "micro mode" for the motion capabilities described above to work, there are string capabilities defined to contain the control sequence to enter and exit this mode.
terminfo(4) terminfo(4) (ENHANCED CURSES) Two miscellaneous capabilities complete the list of motion capabilities. One of these is needed for printers that move the current position to the beginning of a line when certain control characters, such as linefeed or formfeed, are used. The other is used for the capability of suspending the motion that normally occurs after printing a character.
terminfo(4) terminfo(4) (ENHANCED CURSES) Enhanced Printing sshm Enter shadow-printing mode rshm Exit shadow-printing mode sitm ritm Enter italicizing mode Exit italicizing mode swidm rwidm Enter wide character mode Exit wide character mode ssupm rsupm supcs Enter superscript mode Exit superscript mode List of characters available as superscripts ssubm rsubm subcs Enter subscript mode Exit subscript mode List of characters available as subscripts If a printer requires the sshm control sequence bef
terminfo(4) terminfo(4) (ENHANCED CURSES) Alternate Character Sets scs Select character set N scsd Start definition of character set N, M characters defc Define character A, B dots wide, descender D rcsd End definition of character set N csnm List of character set names daisy Printer has manually changed print-wheels The scs, rcsd, and csnm strings are used with a single argument, N, a number from 0 to 63 that identifies the character set.
terminfo(4) terminfo(4) (ENHANCED CURSES) Dot-Matrix Graphics npins Number of pins, N, in print-head spinv Spacing of pins vertically in pins per inch spinh Spacing of dots horizontally in dots per inch porder Matches software bits to print-head pins sbim Start printing bit image graphics, B bits wide rbim End printing bit image graphics The sbim string is used with a single argument, B, the width of the image in dots.
terminfo(4) terminfo(4) (ENHANCED CURSES) Changing the Character/Line Pitches cpi Change character pitch cpix If set, cpi changes spinh lpi lpix Change line pitch If set, lpi changes spinv Programs that use cpi or lpi should recalculate the dot spacing: Effects of Changing the Character/Line Pitches Before After Using cpi with cpix clear: spinh’ spinh Using cpi with cpix set: spinh’ spinh = spinh’ * orhi / orhi’ Using lpi with lpix clear: spinv’ spinv Using lpi with lpix set: spinv’ spinv = spinv’ * orh
terminfo(4) terminfo(4) (ENHANCED CURSES) Note that most printer manufacturers advertise the maximum print rate, not the nominal print rate. A good way to get a value to put in for cps is to generate a few pages of text, count the number of printable characters, and then see how long it takes to print the text. Applications that use these values should recognize the variability in the print rate.
terminfo(4) terminfo(4) (ENHANCED CURSES) applications can use Curses to invoke those features, and can take advantages of optimizations within Curses and thus operate more efficiently. For most terminals, an optimal terminfo entry has already been written. EXTERNAL INFLUENCES Environment Variables CC Specifies a substitute character for a prototype command character. See cmdch in the "Miscellaneous" subsection of the "Insert/Delete Line" section.
term_c(4) term_c(4) NAME term.h - terminal capabilities DESCRIPTION The header contains definitions for each of the following symbolic constants and capability names in the following tables. In the following table, a Variable is the name by which a C programmer accesses a capability (at the terminfo level). A Capname is the short name for a capability specified in the terminfo source file. It is used by a person updating the source file and by the tput command.
term_c(4) term_c(4) status_line_esc_ok eslok es Escape can be used on the status line tilde_glitch hz hz Hazeltine; can’t print tilde (˜) transparent_underline ul ul Underline character overstrikes xon_xoff xon xo Terminal uses xon/xoff handshaking Numbers Cap- Termcap Variable name Code Description bit_image_entwining bitwin Yo Number of passes for each bit-map row bit_image_type bitype Yp Type of bit image device buffer_capacity bufsz Ya Number of bytes buffered before p
term_c(4) A tA term_c(4) change_scroll_region csr cs Change to lines #1 through #2 (vt100) char_padding rmp rP Like ip but when in replace mode char_set_names csnm Zy List of character set names clear_all_tabs tbc ct Clear all tab stops clear_margins mgc MC Clear all margins (top, bottom, and sides) clear_screen clear cl Clear screen and home cursor clr_bol el1 cb Clear to beginning of line, inclusive clr_eol el ce Clear to end of line clr_eos ed cd Clear to end of dis
term_c(4) term_c(4) enter_shadow_mode sshm ZM Enable shadow printing enter_standout_mode smso so Begin standout mode enter_subscript_mode ssubm ZN Enable subscript printing enter_superscript_mode ssupm ZO Enable superscript printing enter_top_hl_mode ethlm n/a Turn on top highlight mode enter_underline_mode smul us Start underscore mode enter_upward_mode sum ZP Enable upward carriage motion enter_vertical_hl_mode evhlm n/a turn on vertical highlight mode enter_xon_mode smx
term_c(4) A tA term_c(4) key_cancel kcan @2 sent by cancel key key_catab ktbc ka sent by clear-all-tabs key key_clear kclr kC sent by clear-screen or erase key key_close kclo @3 sent by close key key_command kcmd @4 sent by cmd (command) key key_copy kcpy @5 sent by copy key key_create kcrt @6 sent by create key key_ctab kctab kt sent by clear-tab key key_dc kdch1 kD sent by delete-character key key_dl kdl1 kL sent by delete-line key key_down kcud1 kd sent by t
term_c(4) term_c(4) key_f41 kf41 FV sent by function key f41 key_f42 kf42 FW sent by function key f42 key_f43 kf43 FX sent by function key f43 key_f44 kf44 FY sent by function key f44 key_f45 kf45 FZ sent by function key f45 key_f46 kf46 Fa sent by function key f46 key_f47 kf47 Fb sent by function key f47 key_f48 kf48 Fc sent by function key f48 key_f49 kf49 Fd sent by function key f49 key_f50 kf50 Fe sent by function key f50 key_f51 kf51 Ff sent by function key
term_c(4) A tA term_c(4) key_seol kEOL *8 sent by shifted clear-line key key_sexit kEXT *9 sent by shifted exit key key_sf kind kF sent by scroll-forward/down key key_sfind kFND *0 sent by shifted find key key_shelp kHLP #1 sent by shifted help key key_shome kHOM #2 sent by shifted home key key_sic kIC #3 sent by shifted input key key_sleft kLFT #4 sent by shifted left-arrow key key_smessage kMSG %a sent by shifted message key key_smove kMOV %b sent by shifted move
term_c(4) term_c(4) parm_down_cursor cud DO Move down #1 lines. parm_down_micro mcud Zf Like parm_down_cursor for micro adjust. parm_ich ich IC Insert #1 blank chars parm_index indn SF Scroll forward #1 lines. parm_insert_line il AL Add #1 new blank lines parm_left_cursor cub LE Move cursor left #1 spaces parm_left_micro mcub Zg Like parm_left_cursor for micro adjust. parm_right_cursor cuf RI Move right #1 spaces.
term_c(4) term_c(4) set_right_margin_parm smgrp Zn Set right margin at column #1 set_tab hts st Set a tab in all rows, current column set_tb_margin smgtb MT Sets both top and bottom margins set_top_margin smgt Zo Set top margin at current line set_top_margin_parm smgtp Zp Set top (bottom) margin at line #1 (#2) set_window wind wi Current window is lines #1-#2 cols #3-#4 start_bit_image sbim Zq Start printing bit image graphics start_char_set_def scsd Zr Start definition of a
ttys(4) ttys(4) NAME ttys - terminal control database file, for trusted systems SYNOPSIS /tcb/files/ttys DESCRIPTION The system supports a single terminal control database containing entries for each local terminal that can log into the system. Authentication programs use information contained in the terminal control database to determine if login from the terminal is permitted. Additional fields are maintained for informational purposes.
ttys(4) ttys(4) AUTHOR ttys was developed by HP. FILES /tcb/files/ttys Terminal control database file SEE ALSO login(1), getprtcent(3), devassign(4), authcap(4), default(4).
ttytype(4) ttytype(4) NAME ttytype - data base of terminal types by port SYNOPSIS /etc/ttytype DESCRIPTION ttytype is a database that identifies the kind of terminal that is attached to each tty port on the system. The file contains one line per port, and each line contains the terminal type (as a name listed in terminfo (4)), a space, and the name of the tty device file, less the initial /dev/.
tunefstab(4) tunefstab(4) NAME tunefstab - VxFS file system tuning parameters table DESCRIPTION The tunefstab file contains tuning parameters for VxFS file systems. tunefs sets the tuning parameters for mounted file systems by processing command line options or by reading parameters in the tunefstab file.
tztab(4) tztab(4) NAME tztab - time zone adjustment table for date(1) and ctime(3C) DESCRIPTION The tztab file describes the differences between Coordinated Universal Time (UTC) and local time. Several local areas can be represented simultaneously with historical detail. The file tztab consists of one or more time zone adjustment entries. The first line of the entry contains a unique string that may match the value of the TZ string in the user’s environment.
tztab(4) tztab(4) SEE ALSO date(1), ctime(3C), environ(5).
ups_conf(4) ups_conf(4) NAME ups_conf - HP PowerTrust Uninterruptible Power System (UPS) monitor configuration file DESCRIPTION The default configuration file for the HP PowerTrust UPS monitor daemon (ups_mond). Another file can be used as long as it complies with the specified format, and the monitor daemon is configured to use the alternate file (see the description of the -f option in ups_mond (1M)).
ups_conf(4) ups_conf(4) FILES /dev/tty* /etc/ups_conf SEE ALSO ups_mond(1M).
utmp(4) utmp(4) (TO BE OBSOLETED) NAME utmp, wtmp, btmp - utmp, wtmp, btmp entry format SYNOPSIS #include #include DESCRIPTION These files, which hold user and accounting information for such commands as last, who, write, and login (see last (1), who(1), write (1), and login (1)), have the following structure as defined by
utmp(4) utmp(4) (TO BE OBSOLETED) FILES /etc/utmp /var/adm/wtmp /var/adm/btmp AUTHOR utmp, wtmp, and btmp were developed by HP and the University of California, Berkeley. SEE ALSO last(1), login(1), who(1), write(1), acctcon(1M), fwtmp(1M), utmpd(1M), getut(3C), getuts(3C), getutx(3C). STANDARDS CONFORMANCE
utmps(4) utmps(4) NAME utmps - user-accounting database SYNOPSIS #include #include DESCRIPTION File utmps contains user accounting information for all users logged onto the system. This file will be accessed by getuts (3C) only if utmpd (1M) is not running.
utmpx(4) utmpx(4) NAME utmpx - utmpx database storage file SYNOPSIS #include #include DESCRIPTION File utmpx contains user accounting information for all users logged onto the system. This file will be used instead of the utmp file, which is being depreciated.
uuencode(4) uuencode(4) NAME uuencode - format of an encoded uuencode file DESCRIPTION Files output by uuencode consist of a header line followed by a number of body lines, and a trailer line. The uudecode command ignores any lines preceding the header or following the trailer (see uuencode (1)). Lines preceding a header must not look like a header. The header line consists of the word begin followed by a space, a mode (in octal), another space, and a string which specifies the name of the remote file.
wtmps(4) wtmps(4) NAME wtmps, btmps - user login information SYNOPSIS #include #include DESCRIPTION wtmps and btmps hold user and accounting information for such commands as last, who, write, and login (see last (1), who(1), write (1), and login (1)). File btmps contains bad login entries for each invalid logon attempt. File wtmps contains a record for all logins and logouts apart from accounting records.
ypfiles(4) ypfiles(4) NAME ypfiles - Network Information Service database and directory structure DESCRIPTION Remarks The Network Information Service (NIS) was formerly known as Yellow Pages (yp). Although the name has changed, the functionality of the service remains the same. The Network Information Service (NIS) network lookup service uses databases in the directory hierarchy under /var/yp. These databases exist only on machines that act as NIS servers.
ypfiles(4) ypfiles(4) Standard NIS Mapname Abbreviated Mapname mail.aliases mail.byaddr ethers.byaddr ethers.byname group.bygid group.byname mail.alias mail.byad ether.byad ether.byna group.bygi group.byna hosts.byaddr hosts.byname netgroup netgroup.byhost netgroup.byuser netid.byname networks.byaddr networks.byname passwd.byname passwd.byuid protocols.byname protocols.bynumber publickey.byname rpc.byname rpc.bynumber services.byname auto.master ypservers hosts.byad hosts.byna netgroup netgr.
ypfiles(4) ypfiles(4) General NIS Mapname ASCII Source aliases /etc/mail/aliase ethers Standard NIS Mapname mail.aliases mail.byaddr ethers.byaddr ethers.byname group.byname group.bygid hosts.byname hosts.byaddr netgroup netgroup.byhost netgroup.byuser netid.byname network.byaddr network.byname passwd.byname passwd.byuid protocols.byname protocols.bynumber publickey.byname rpc.byname rcp.bynumber servi.bynp services.byname auto.
(Notes) A (Notes) yA Section 4−−372 Hewlett-Packard Company −1− HP-UX 11i Version 2: August 2003
