HP-UX Reference Section 4: File Formats HP-UX 11i Version 1, September 2005 Update Volume 8 of 10 Manufacturing Part Number : B2355-90909 Printed In USA E0905 Printed in USA © Copyright 1983-2005 Hewlett-Packard Development Company LP.
Legal Notices The information in this document is subject to change without notice. Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. U.S. Government License Confidential computer software.
Copyright 1996 Morning Star Technologies, Inc. Copyright 1996 Progressive Systems, Inc. Trademark Notices Intel and Itanium are registered trademarks of Intel Corporation in the US and other countries and are used under license. Java is a US trademark of Sun Microsystems, Inc. Microsoft and MS-DOS are U.S. registered trademarks of Microsoft Corporation. OSF/Motif is a trademark of The Open Group in the US and other countries. UNIX is a registered trademark of The Open Group.
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 Release; Date; Format; Distribution B2355-60127 HP-UX 11i Version 1; September 2005 Update; one volume HTML; http://docs.hp.com and Instant Information.
Typographical Conventions audit (5) An HP-UX manpage. audit is the name and 5 is the section in the HP-UX Reference. On the web and on the Instant Information CD, it may be a hot link to the 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.
vi
Preface HP-UX is the Hewlett-Packard Company’s implementation of a UNIX operating system that is compatible with various industry standards. It is based on the System V Release 4 operating system and includes important features from the Fourth Berkeley Software Distribution. The ten volumes of this manual contain the system reference documentation, made up of individual entries called manpages, named for the man command (see man (1)) 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 ................... hosts.equiv(4) password file format .......................................................................................................
Table of Contents Volume Eight Entry Name(Section): name Description master(4): master ............................................................................. master kernel configuration information mnttab(4): mnttab ................................................................................................... mounted file system table model(4): model ..................................................................................................
Table of Contents Volume Eight Entry Name(Section): name Description terminfo(4): terminfo ........................................................ printer, terminal, and modem capability database ttys(4): ttys ........................................................................................................ terminal control database file ttytype(4): ttytype ................................................................................... data base of terminal types by port tun(4): tun .............
Notes xii Hewlett-Packard Company HP-UX 11i Version 1: September 2005
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 the directories /usr/include or /usr/include/sys. SEE ALSO hier(5), introduction(9). 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 a #include (for ELF files) #include (for SOM files) 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 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 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.
a.out(4) int unsigned int a.out(4) 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 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) packed decimal struct/array 16 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) a #define #define #define #define #define #define #define #define a.
a.out(4) a.out(4) 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. R_DLT_REL Copy one instruction word with relocation. The word is assumed to be a register-18-relative load or store instruction (for example, LDW , LDO , STW ).
a.out(4) a.out(4) RS´, RD´, or RR´ may be used. a 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´). This setting remains in effect until explicitly changed or until the end of the subspace. R_D_MODE Select round-up mode (LD´/RD´).
a.out(4) a.out(4) 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. This fixup is used to identify three-instruction sequences to access data (for importing shared library data).
a.out(4) a.
a.out(4) R_TP_OVERRIDE R_RESERVED a.out(4) 222 224-255 1 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. The encoding for such calls is simply the number of parameters in general registers (0 to 4), plus 5 if there is a return value in a general register.
acct(4) acct(4) NAME acct - per-process accounting file format SYNOPSIS a #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. SEE ALSO acct(2), acct(1M), acctcom(1M), exec(2), fork(2).
ar(4) ar(4) NAME ar - common archive file format SYNOPSIS a #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)). 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) yetanotherlongfilename.o contains /27 in the ar_name field. The long name string table would have the following format: 0 10 20 30 40 50 SEE ALSO System Tools: ar(1) ld(1) Miscellaneous: a.out(4) magic(4) ranlib(1) strip(1) +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 | .
arraytab(4) arraytab(4) NAME arraytab - disk array configuration table a DESCRIPTION Arraytab is a table of supported configurations for HP SCSI disk array products. Each table entry includes a set of parameter values that specify an array configuration. The array configuration table is located in /etc/hpC2400/arraytab. HP SCSI disk array devices are highly configurable.
arraytab(4) RAID_3: RAID_5: arraytab(4) This level uses byte striping across a set of n drives, with an additional drive maintaining an XOR parity check byte for each byte of data. The resulting logical disk sector size is n times the sector size of one disk. Data can be recovered, if a drive fails, by using the redundancy of the parity drive while operating in a ‘‘degraded’’ mode.
arraytab(4) a arraytab(4) sequence label dN, where N is a number from 0 to 4. Subsequent lists may be used to create drive groups larger than 5 disks. The disk identifier label is a string formed from the vendor ID and product ID strings returned from a SCSI Inquiry message, separated by ‘‘_’’. Certain constraints are made for the drive groups and drive lists, depending upon the number of drives and the RAID level chosen. See restrictions below. lp num Logical partition within the logical configuration.
arraytab(4) arraytab(4) Bit 3 off Not used. Bit 4 on Asynchronous Event Notification polling enable. Bit 5 on Parity verification enable. Bit 6 on Write with parity verification enable. Bit 7 off Not used. Bit 8 off Mode Sense: Current. Current values are accessed during mode sense. This bit should not be set concurrently with Bit 9. Bit 9 off Mode Sense: Saved. Saved values are accessed during mode sense. This bit should not be set concurrently with Bit 10.
arraytab(4) arraytab(4) For configurations using logical partitions exceeding 2 GB it is necessary that the 2 GB governor flag be turned off in the array controller. See see(1M). a DEPENDENCIES: Series 700: LUN address 6 and 7 are reserved for use with array management utilities, and should not be configured. Series 800: LUN address 6 and 7 are reserved for use with array management utilities, and should not be configured. Only RAID levels 0 (Independent), 3, and 5 are supported.
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: 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 a #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 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 a 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.
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) b # # # # 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. Refer to other inode(4) manual pages for information regarding the inode structure for other file systems. 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. c 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) 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. Multiple directory hierarchies can be placed on a single volume, or a single directory hierarchy can span multiple volumes.
cdrom(4) cdrom(4) 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. Extended Attribute Records An extended attribute record (abbreviated XAR ) is a data structure specifying additional information about the file or directory with which the XAR is associated.
cdrom(4) Level 2 cdrom(4) 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 CD-ROM. The levels are: Level 1 Each file consists of a single file section. File names contain no more than eight characters, and file name extensions contain no more than three.
charmap(4) charmap(4) NAME charmap - symbolic translation file for localedef scripts SYNOPSIS localedef -f charmap locale_name c 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 c 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 short 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]; c char } Hdr; 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 d 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. d 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 d 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. Its use is discouraged.
dosif(4) dosif(4) NAME DOSIF - DOS Interchange Format description DESCRIPTION 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. The DOS utilities described in Section 1 (referred to hereafter as dos∗(1)) are provided for reading data from and writing data to DOSIF volumes. Use these utilities to retrieve information from a DOSIF volume.
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. d pseudonym This field is the absolute path of the device file known to the system and the end-user application.
dp(4) dp(4) SEE ALSO dpp(1M), ocd(1M), ocdebug(1M), syslog(3C), pcf(4), ddfa(7).
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)). e /etc/exports is read automatically by the exportfs command (see exportfs(1M)).
exports(4) exports(4) Currently HP-UX will allow a match for a non-fully qualified hostname; this HPonly 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.
fs(4) fs(4) NAME fs - format of file system volume SYNOPSIS #include #include #include #include #include #include DESCRIPTION Every file system storage volume has a common format for certain vital information. The first 8 kbytes on a volume contain a volume header which identifies that volume as a Logical Interchange Format (LIF) volume. Such volume may be divided into a number of sections.
fs(4) f fs(4) /* sizes determined by number of cylinder groups and their sizes */ daddr_t fs_csaddr; /* blk addr of cyl grp summary area */ long fs_cssize; /* size of cyl grp summary area */ long fs_cgsize; /* cylinder group size */ /* these fields should be derived from the hardware */ long fs_ntrak; /* tracks per cylinder */ long fs_nsect; /* sectors per track */ long fs_spc; /* sectors per cylinder */ /* this comes from the disk driver partitioning */ long fs_ncyl; /* cylinders in file system */ /* th
fs(4) fs(4) Cylinder-Group-Related Limits Each cylinder keeps track of the availability of blocks at different rotational positions, so that sequential blocks can be laid out with minimum rotational latency. NRPOS is the number of rotational positions which are distinguished. For example, with NRPOS 8 the resolution of the summary information is 2ms for a typical 3600 rpm drive. fs_rotdelay gives the minimum number of milliseconds to initiate another disk transfer on the same cylinder.
fs(4) fs(4) SEE ALSO inode(4), lif(4).
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).
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) noretrieve filename filename .... Always deny retrievability of these files. If the files are an absolute path specification (i.e. begins with / character), then only those files are marked unretrievable. Otherwise all files with the matching filename are refused transfer. Example: noretrieve /etc/passwd core specifies that no one is able to get the file /etc/passwd , whereas they are allowed to transfer a file, passwd , if it is not in /etc .
ftpaccess(4) %u %U %M %N ftpaccess(4) username as determined via RFC931 authentication username given at login time maximum allowed number of users in this class current number of users in this class The message will only be displayed once to avoid annoying the user. Remember that when messages are triggered by an anonymous FTP user, the path must be relative to the base of the anonymous FTP directory tree.
ftpaccess(4) ftpaccess(4) cdpath dir Defines a directory entry in the cdpath . dir defines a search path that is used when changing directories. For example: cdpath /pub/packages cdpath /.aliases would allow the user to cd into any directory directly under /pub/packages or /.aliases directories. The search path is defined by the order in which the lines appear in the /etc/ftpd/ftpaccess file. If the user were to give the command: cd foo The directory will be searched for in the following order: .
ftpaccess(4) ftpaccess(4) Permission Capabilities chmod yes|no typelist delete yes|no typelist overwrite yes|no typelist rename yes|no typelist umask yes|no typelist 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 and real . passwd-check none | trivial | rfc822 [ enforce | warn ] Define the level and enforcement of password checking done by the server for anonymous ftp.
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. f deny username addrglob [ addrglob ... ] Always deny host(s) matching addrglob to log in as username.
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) 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) implemented (such as RIP support of the policy option). 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.
gated.conf(4) gated.conf(4) directory identified by pathname for any included files that do not have a fully qualified filename, such as files that do not begin with "/". This statement does not actually change the 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.
gated.conf(4) g gated.
gated.conf(4) gated.conf(4) 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. passive Prevents GateD from changing the preference of the route to this interface if it is not believed to be functioning properly due to lack of received routing information.
gated.conf(4) gated.conf(4) 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. Unix interfaces consist of the name of the device driver, like ie, and a unit number, like 0, 5 or 22.
gated.conf(4) gated.conf(4) 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 insures that there is a route available to each IP interface that is configured and up. Normally this this done by the ifconfig command that configures the interface; GateD does it to insure consistency.
gated.conf(4) gated.conf(4) 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: g • 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. • The interface statement tells GateD not to mark interface 128.66.12.
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) [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) 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. The kernel metric will not be added.
gated.conf(4) other gated.conf(4) 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. The HELLO protocol is an interior protocol that uses a routing metric based on the length of time it takes a packet to make the trip between the source and the destination.
gated.conf(4) gated.conf(4) [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. broadcast Specifies that HELLO packets will be broadcast regardless of the number of interfaces present.
gated.conf(4) gated.conf(4) 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. But if the trustedgateways clause is specified only updates from the gateways in the list are accepted.
gated.conf(4) gated.conf(4) values explicitly, it is ill-advised to do so. Hardware multicast capabilities are also used where possible to deliver link-status messages. OSPF areas are connected by the backbone area, the area with identifier 0.0.0.0. All areas must be logically contiguous and the backbone is no exception. To permit maximum flexibility, OSPF allows the configuration of virtual links enable the backbone area to appear contiguous despite the physical reality.
gated.conf(4) gated.conf(4) }; 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) configured, at least one must the be backbone. The backbone may only be configured using the backbone keyword, it may not be specified as area 0. The backbone interface may be a virtuallink. authtype 0 | 1 | none | simple OSPF specifies an authentication scheme per area. Each interface in the area must use this same authentication scheme although it may use a different authenticationkey.
gated.conf(4) gated.conf(4) 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. It is specified by one to eight decimal digits separated by periods, a one to eight byte hexadecimal string preceded by 0x, or a one to eight character string in double quotes.
gated.conf(4) gated.conf(4) reachability indications, not true metrics. EGP updates contain metrics, called distances which range from 0 to 255. GateD will only compare EGP distances learned from the same AS. them. Before EGP sends routing information to a remote router, it must establish an adjacency with that router. This is accomplished by an exchange of Hello (not to be confused with the HELLO protocol, or OSPF HELLO messages) and I Heard You (I-H-U) messages with that router.
gated.conf(4) gated.conf(4) and the EGP specific tracing options below.) group EGP neighbors must be specified as members of a group. A group is usually used to group all neighbors in one autonomous system. Parameters specified on the group clause apply to all of the subsidiary neighbors unless explicitly overridden on a neighbor clause. Any number of group clauses may specify any number of neighbor clauses.
gated.conf(4) gated.conf(4) lcladdr local_address Specifies the address to be used on the local end of the connection with the neighbor. The local address must be on an interface which is shared with the neighbor or with the gateway of the neighbor when the gateway parameter is used. A session will only be opened when an interface with the appropriate local address (through which the neighbor or gateway address is directly reachable) is operating.
gated.conf(4) gated.conf(4) BGP supports two basic types of sessions between neighbors, internal (sometimes referred to as IBGP) and external. Internal sessions are run between routers in the same autonomous system, while external sessions run between routers in different autonomous systems. When sending routes to an external peer the local AS number is prepended to the AS path, hence routes received from an external peer are guaranteed to have the AS number of that peer at the start of the path.
gated.conf(4) g gated.
gated.conf(4) gated.conf(4) Groups BGP peers are grouped by type and the autonomous system of the peers. Any number of groups may be specified, but each must have a unique combination of type and peer autonomous system. There are four possible group types: group type external peeras autonomous_system In the classic external BGP group, full policy checking is applied to all incoming and outgoing advertisements.
gated.conf(4) gated.conf(4) Specifying peers Within a group, BGP peers may be configured in one of two ways. They may be explicitly configured with a peer statement, or implicitly configured with the allow statement. Both are described here: allow The allow clauses allows for peer connections from any addresses in the specified range of network and mask pairs. All parameters for these peers must be configured on the group clause.
gated.conf(4) gated.conf(4) version version Specifies the version of the BGP protocol to use with this peer. If not specified, the highest supported version is used first and version negotiation is attempted. If it is specified, only the specified version will be offered during negotiation. Currently supported version are 2, 3 and 4. passive Specifies that active OPENs to this peer should not be attempted. GateD should wait for the peer to issue an open.
gated.conf(4) gated.conf(4) BGP global trace options. (See Trace Statements and the BGP specific tracing options below.) Tracing options Note that the state option works with BGP, but does not provide true state transition information. Packet tracing options (which may be modified with detail, send and recv): packets All BGP packets open BGP OPEN packets which are used to establish a peer relationship. update BGP UPDATE packets which are used to pass network reachability information.
gated.conf(4) gated.conf(4) If GateD has determined that the state of the kernel forwarding table has been changed, the necessary requests to the kernel are made to restore the correct state. Note that on currently available systems it is not possible to disable the processing of ICMP redirects, even when the system is functioning as a router. To ignore the effects of redirects, GateD must process each one and actively restore any changes it made to the state of the kernel.
gated.conf(4) gated.conf(4) The Router Discovery Server The Router Discovery Server runs on routers and announces their existence to hosts. It does this by periodically multicasting or broadcasting a Router Advertisement to each interface on which it is enabled. These Router Advertisements contain a list of all the routers addresses on a given interface and their preference for use as a default router. Initially these Router Advertisements occur every few seconds, then fall back to every few minutes.
gated.conf(4) gated.conf(4) addresses. advertise Specifies that the specified address(es) should be included in Router Advertisements. This is the default. ignore Specifies that the specified address(es) should not be included in Router Advertisements. broadcast Specifies that the given address(es) should be included in a broadcast Router Advertisement because this system does not support IP multicasting, or some hosts on attached network do not support IP multicasting.
gated.conf(4) gated.conf(4) }]; traceoptions trace_options Specifies the tracing options for OSPF. (See Trace Statements and the OSPF specific tracing options below.) preference preference ; Specifies the preference of all Router Discovery default routes. The default is 55. interface interface_list Specifies the parameters that apply to physical interfaces. Note a slight difference in convention from the rest of GateD, interface specifies just physical interfaces (such as le0, ef0 and en1).
gated.conf(4) gated.conf(4) Forwarding tables and Routing tables The table in the kernel that controls the forwarding of packets is a forwarding table, also know in ISO speak as a forwarding information base, or FIB. The table that GateD uses internally to store routing information it learns from routing protocols is a routing table, known in ISO speak as a routing information base, or RIB. The routing table is used to collect and store routes from various protocols.
gated.conf(4) gated.conf(4) There are compilation time and configuration time options that cause delete and add sequences to be used in lieu of change messages. Expandable New levels of kernel/GateD communications may be added by adding new message types. Reading the Forwarding Table When GateD starts up it reads the kernel forwarding table and installs corresponding routes in the routing table.
gated.conf(4) gated.conf(4) When this method is in use, GateD re-reads the interface list only once a minute. It also re-reads it on routing table changes indications and when a SIGUSR2 is received. This interval may be explicitly configured in the interface configuration. Reading interface physical addresses Later version of the getkerninfo() and sysctl() interfaces return the interface physical addresses as part of the interface information.
gated.conf(4) gated.conf(4) 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. noflushatexit During normal shutdown processing GateD deletes all routes from the kernel forwarding table that do not have a retain indication.
gated.conf(4) gated.conf(4) the flash update processing. The default is lower which means that flash updates are processed first. To process kernel updates at the same priority as flash updates, specify flash; to process them at a lower priority, use lower. Tracing options While the kernel interface is not technically a routing protocol, in many cases it is handled as one.
gated.conf(4) gated.conf(4) route competes with routes from other protocols. The default preference is 60. retain Normally gated removes all routes except interface routes from the kernel forwarding table during a graceful shutdown. The retain option may be used to prevent specific static routes from being removed. This is useful to insure that some routing is available when gated is not running.
gated.conf(4) gated.conf(4) network mask mask [ exact | refines ] network masklen number [ exact | refines ] Matching usually requires both an address and a mask, although the mask is implied in the shorthand forms listed below. These three forms vary in how the mask is specified. In the first form, the mask is implied to be the natural mask of the network. In the second, the mask is explicitly specified. In the third, the mask is specified by the number of contiguous one bits.
gated.conf(4) gated.conf(4) AS path terms An AS path term is one of the following three objects: autonomous_system . ( aspath_regexp ) where autonomous_system Any valid autonomous system number, from one through 65534 inclusive. . Matches any autonomous system number.
gated.conf(4) gated.conf(4) Route Filters All the formats allow route filters as shown below. See the section on route filters for a detailed explanation of how they work. When no route filtering is specified (when restrict is specified on the first line of a statement), all routes from the specified source will match that statement. If any filters are specified, only routes that match the specified filters will be imported.
gated.conf(4) gated.conf(4) }; Due to the nature of OSPF, only the importation of ASE routes may be controlled. OSPF intra- and interarea routes are always imported into the gated routing table with a preference of 10. If a tag is specified, the import clause will only apply to routes with the specified tag. It is only possible to restrict the importation of OSPF ASE routes when functioning as an AS border router. This is accomplished by specifying an export ospfase clause.
gated.conf(4) gated.conf(4) Exporting to EGP and BGP export proto bgp | egp as autonomous system restrict ; export proto bgp | egp as autonomous system [ metric metric ] { export_list ; }; Exportation to EGP and BGP is controlled by autonomous system, the same policy is applied to all routers in the AS. EGP metrics range from 0 to 255 inclusive with 0 being the most attractive. BGP metrics are 16 bit unsigned quantities. They range from 0 to 65535 inclusive with 0 being the most attractive.
gated.conf(4) gated.conf(4) OSPF ASE routes also have the provision to carry a tag. This is an arbitrary 32 bit number that can be used on OSPF routers to filter routing information. See the OSPF protocol configuration for detailed information on OSPF tags. The default tag specified by the ospf defaults clause may be overridden by a tag specified on the export statement. Specifying the source The export list specifies export based on the origin of a route and the syntax varies depending on the source.
gated.conf(4) gated.conf(4) Non-routing by protocol proto default | aggregate restrict ; proto default | aggregate [ metric metric ] { route_filter [ restrict | ( metric metric ) ] ; }; These protocols may only be referenced by protocol. default Refers to routes created by the gendefault option. It is recommended that route generation be used instead. aggregate Refers to routes synthesized from other routes when the aggregate and generate statements are used.
gated.conf(4) gated.conf(4) only possible on systems with support for reject routes. A slight variation of aggregation is the generation of a route based on the existence of certain conditions. This is sometimes known as the route of last resort. This route inherits the next hops and aspath from the contributor specified with the lowest (most favorable) preference. The most common usage for this is to generate a default based on the presence of a route from a peer on a neighboring backbone.
gated.conf(4) gated.conf(4) route_filter See below. A route may only contribute to an aggregate route which is more general than itself; it must match the aggregate under its mask. Any given route may only contribute to one aggregate route, which will be the most specific configured, but an aggregate route may contribute to a more general aggregate. Route Filters All the formats allow route filters as shown below. See the section on route filters for a detailed explanation of how they work.
gated.conf(4) gated.conf(4) gateway An intermediate destination by which packets are delivered to their ultimate destination. A host address of another router that is directly reachable via an attached network. As with any host address it may be specified symbolically. gateway_list A list of one or more gateways separated by white space. HELLO One of a class of interior gateway protocols, described in more detail in the HELLO section of the Protocol Overview. host g The IP address of any host.
gated.conf(4) gated.conf(4) SAMPLE ROUTING PROTOCOL METRICS Protocol Metric Represents -------- ----------------RIP distance (hop-count) HELLO delay (milliseconds) OSPF cost of path ISIS cost of path EGP distance (unused) BGP unspecified Range ----0-15 0-29999 0-????? 0-254 0-65535 0-65534 Unreachable ----------16 30000 Delete Delete 255 65535 multiaccess networks Those physical networks that support the attachment of multiple (more than two) routers.
gated.conf(4) gated.conf(4) prefix A contiguous mask covering the most significant bits of an address. The prefix length specifies how many bits are covered. QoS quality of service The OSI equivalent of TOS. RIP Routing Information Protocol One of a class of interior gateway protocols, described in more detail in the RIP section of the Protocol Overview. router id A 32-bit number assigned to each router running the OSPF protocol. This number uniquely identifies the router within the autonomous system.
gated.conf(4) SEE ALSO RFC 827: RFC 891: gated.conf(4) E. Rosen, Exterior Gateway Protocol EGP D. Mills, DCN local-network protocols RFC 904: D. Mills, Exterior Gateway Protocol formal specification RFC 1058: C. Hedrick, Routing Information Protocol RFC 1105: K. Lougheed, Y. Rekhter, Border Gateway Protocol BGP RFC 1163: K. Lougheed, Y. Rekhter, A Border Gateway Protocol (BGP) RFC 1164: J. Honig, D. Katz, M. Mathis, Y. Rekhter, J.
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 newline. 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) 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. h /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) If service name is rpc (NFS RPC services), two extra fields are required. They must appear between the server program field and the server program arguments field: 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 (-).
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 getipnodebyaddr().
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: i 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. i 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(4) inode(4) NAME inode - format of an inode SYNOPSIS #include #include DESCRIPTION An inode for a plain file or directory in a file system has the following structure as it appears on a disk block, defined in .
inode(4) inode(4) SEE ALSO stat(2), fs(4), types(5).
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; } dyn_major_t; /* Must be _DYN_MAJOR" */" /* Driver name */ 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) default_domain This relation identifies the default domain for the hosts in the realm. This is needed for translating V4 principal names (which do not contain a domain name) to V5 principal names (which do contain a domain name). v4_instance_convert This subsection allows the administrator to configure exceptions to the default_domain mapping rule.
krb5.conf(4) krb5.conf(4) LOG_ALERT LOG_EMERG LOG_CRIT LOG_DEBUG LOG_ERR LOG_INFO LOG_NOTICE LOG_WARNING For example, to specify LOG_CRIT severity, one would use CRIT for severity . The LOG_ prefix is deleted. The facility argument specifies the facility under which the messages are logged. This may be any of the following facilities supported by the syslog() call (see syslog(3C)).
krb5.conf(4) krb5.conf(4) The [capaths] section of the configuration file used on NERSC.GOV systems would look like this: [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.NET } } k In the above examples, the ordering is not important, except when the same subtag name is used more then once.
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 # 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.
libgss(4) libgss(4) gss_verify_mic: To verify message integrity. 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.
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).
loadmods(4) loadmods(4) NAME loadmods - loadable modules to load into the running kernel during boot DESCRIPTION The /etc/loadmods file contains the names of dynamically loadable kernel modules that are loaded into the running kernel at boot time. If the system administrator wants a dynamically loadable kernel module to be demand loaded on every system reboot, s/he may add the name of the module to this file. If the /etc/loadmods file is present at boot time, the /sbin/init.
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) 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) 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 currency_symbol or int_curr_symbol. 2 The sign string succeeds the quantity and the currency_symbol or int_curr_symbol. 3 The sign string precedes the currency_symbol or succeeds the currency_symbol or int_curr_symbol. 4 The sign string int_curr_symbol.
localedef(4) localedef(4) t_fmt_ampm The operand is a string defining the appropriate time representation in the 12hour 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. Each string should conform to the following format: direction : offset : start_date : end_date : name : format where: direction Either a + or - character.
localedef(4) localedef(4) LC_MESSAGES and END LC_MESSAGES : yesexpr The string operand is an Extended Regular Expression matching acceptable affirmative responses to yes/no queries. noexpr The string operand is an Extended Regular Expression matching acceptable negative responses to yes/no queries. yesstr The string operand identifies the affirmative response for yes/no questions. This keyword is now obsolete and yesexpr should be used instead.
localedef(4) localedef(4) 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 input files are recommended to be written entirely in symbolic names, utilizing a user defined or system-supplied charmap file. This aids portability of localedef input files between different encoded character sets (see charmap(4)).
localedef(4) localedef(4) ’A’ ’a’ ’A’;’A’ # first element of equivalence class ’A’;’a’ # next element of class Two-to-one collating elements are specified by collating-elements defined before the order_start keyword. For example, the two-to-one collating element CH in Spanish, would be defined before the order_start keyword as collating element from "CH" It would then be used in a collating element entry as .
localedef(4) localedef(4) Separators Separator characters include blanks and tabs. Any number of separators can be used to delimit the keywords, metacharacters, constants and strings that comprise a localedef script except that all characters between < and > are considered to be part of the symbolic name even they are s. EXAMPLE Please see the files under /usr/lib/nls/loc/src for examples of locale description files.
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.
master(4) master(4) NAME master - master kernel configuration information DESCRIPTION A master file contains sections of information in a form suitable for config , enabling it to create a kernel configuration file. Master files are found in the directory /usr/conf/master.d. Master files are of two types: • A kernel master file is of the type which usually carries information on several drivers/subsystems. • A kernel module master file carries information on an individual module.
master(4) master(4) 0x004000 0x002000 0x001000 0x000800 0x000400 0x000200 0x000100 0x000080 0x000040 0x000020 0x000010 0x000008 0x000004 0x000002 0x000001 Set STREAMS System V release 3 style open flag (SVR3_OPEN ) Set STREAMS System V release 4 style open flag (SVR4_OPEN ) Autochanger mount routine exists option1 handler exists (Series 700 only) dump handler exists size handler exists link routine exists open handler exists close handler exists read handler exists write handler exists ioctl handler exis
master(4) master(4) $DRIVER_DEPENDENCY Section List of drivers and the other drivers they depend on. Field_1 Dependent driver. Field_2-N Name of supporting drivers or CDIO’s. $DRIVER_LIBRARY Section List of drivers and the library or libraries containing the driver object code. Field_1 Driver name. Field_2-N Name of libraries containing driver code. $LIBRARY Section Library list. List of object code libraries and whether they are required is a minimal system. Field_1 Library name.
master(4) master(4) $VERSION Section Format version. Format version starts from one. Field_1 Version number. (decimal number) Example $VERSION 1 $$$ $LOADABLE Section Capability of a kernel module. If the section exists, the module is dynamically loadable. Otherwise it can be only statically linked into the kernel. Boot device related kernel modules should not supply the section. Kernel module without $LOADABLE section cannot be configured as dynamically loadable module.
master(4) master(4) s m i supports scanning. MP capable driver. Save information to ioconfig. Field_5 block device major number. Field_6 character device major number. Example $TYPE wsio2 stape2 tape c -1 203 $$$ EXAMPLES The following entry in the $DRIVER_INSTALL section will enable the kernel to dynamically assign block and/or character major number(s) for a custom driver, mydriver . mydriver -1 -1 0 FILES /usr/conf/master.
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) NAME model - HP-UX machine identification (deprecated) 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.
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) 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) 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) nettlgen.conf(4) 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. When an individual log file reaches the maximum specified here, the kernel logging system deletes any existing old file, renames the current file to the old file, and starts a new file.
nettlgen.conf(4) nettlgen.conf(4) 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. 9 Subformatter Options C function in the subformatter library to call to get filter options for this subsystem. 10 Group Name A text string to be used in the header banner line in the formatted output.
nettlgen.conf(4) nettlgen.conf(4) are the same as the default. # # KL INFORMATION # KL:500:5000:5M:/var/adm/kl:1 The following example shows a typical subsystem record. These records should not be changed by the user, but are set by the subsystems using nettlconf during product installation.
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) 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 and nlist64 structure formats SYNOPSIS #include Remarks The exact content of the structures 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(3C)).
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 used 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) The default criteria are to continue on anything except SUCCESS; in other words, [SUCCESS=return NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue]. The default, or explicitly specified, criteria are meaningless following the last source in an entry; and are ignored since the action is always to return to the caller irrespective of the status code the source returns.
nsswitch.conf(4) nsswitch.
nsswitch.conf(4) nsswitch.conf(4) Programs that use the get XX by YY () 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) If none of the service modules in the stack are designated as required , then the PAM framework requires that at least one optional or sufficient module succeed. If all fail then the error value from the first service module in the stack is returned. The only exception to the above is caused by the sufficient flag.
pam.conf(4) pam.conf(4) # # PAM configuration # # Authentication management for login service is stacked. # Both UNIX and inhouse authentication functions are invoked. login auth required /usr/lib/security/libpam_unix.1 login auth required /usr/lib/security/libpam_inhouse.1 try_first_pass dtlogin auth required /usr/lib/security/libpam_unix.1 dtlogin auth required /usr/lib/security/libpam_inhouse.1 try_first_pass # # Other services use UNIX authentication other auth required /usr/lib/security/libpam_unix.
pam.conf(4) pam.conf(4) 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. The convention, however, is the following: /usr/lib/security/libpam_service_name .x Implements various function of specific authentication services. /etc/pam.conf Configuration file. /usr/lib/libpam.1 Implements the PAM framework library.
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/libpam_unix.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) 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 64-character 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) 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. Use of the gecos field for keeping user identification information has not been formalized within any of the industry standards.
passwd(4) passwd(4) 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) 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) LP_NO_PAPER (0x31) LP_BUSY (0x32) LP_OFF_LINE (0x34) LP_DATA_ERROR (0x38) ocd ocd ocd ocd ocd continues processing. retries within the limits of the status timer. retries within the limits of the status timer. retries within the limits of the status timer.
pdf(4) pdf(4) NAME pdf - Product Description File DESCRIPTION A Product Description File describes product files contained in the HP-UX operating system. It consists of a file containing a single line entry for each file described, where each entry contains the following fields: pathname owner group mode size links version checksum linked_to Fields are separated by a colon ( : ), and contain the information indicated: p pathname Absolute pathname of the file (starts with / ).
pdf(4) pdf(4) /usr/bin/ls:bin:bin:-r-xr-xr-x:24576:6:66.3:312786007: /usr/bin/ll:::::6:::/usr/bin/ls /usr/bin/su:root:bin:-r-sr-xr-x:90112:1:66.2:3088851439: % total size is 160172 bytes. % total size is 158 blocks. WARNINGS The checksum algorithm is different than that used by the 7.0 Release version of the commands. Use of PDFs is discouraged since this functionality is obsolete and is being replaced with Software Distributor (see sd(4)).
pdgwcfg.conf(4) pdgwcfg.conf(4) (TO BE OBSOLETED) NAME pdgwcfg.conf - HPDPS gateway printer configuration file DESCRIPTION When invoked, the pdgwcfg utility (see pdgwcfg(1M)) reads the configuration information from the /etc/pdgwcfg.conf configuration file. It is used to assist in administering the creation and/or deletion of gateway printers in an HPDPS Basic (non-DCE) environment. /etc/pdgwcfg.
pdgwcfg.conf(4) pdgwcfg.conf(4) (TO BE OBSOLETED) # The logical printer is ’hplaser’ located on ’host2’. # Note: all systems have a DPS spooler named dps_common_spl running # Note: the gateway printer can have the same name as the local # printer for naming consistency across the enterprise.
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 tun(4), 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) p ppp.Dialers(4) \ddd \p \d \K \M \m \c \q Send or receive a character, specified in octal digits. \T Insert the telephone number (found in the fifth field of Systems ) here. Pause for .25 second before proceeding (send only). Delay for two seconds before proceeding (send only). Send a break (.25 second of zero bits). Disable hangups (sets CLOCAL or LNOHANG). enable hangups (unsets CLOCAL or LNOHANG) (the default).
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) ppp.Filter(4) # Describes the default behavior of the daemon: default 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) FE3FF8FFE1FF87 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() returns an array of structures giving privileged group assignments on a per-group-ID basis (see getprivgrp (2)). contains the constants and structures needed to deal with these system calls, and contains: /* * Privileged group definitions -* the numeric values may vary between implementations.
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 Bourne 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. Aliases are other names under which the protocol is also known.
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) prpwd(4) 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. After this time interval the user will no longer be allowed to login. This field is different from the u_life field in that the u_life field is the time from the last password change.
prpwd(4) prpwd(4) EXAMPLES The following is an example of a typical protected password database file: perry:u_name=perry:u_id#101:\ :u_pwd=aZXtu1kmSpEzm:\ :u_minchg#0:u_succhg#653793862:u_unsucchg#622581606:u_nullpw:\ :u_suclog#671996425:u_suctty=tty1:\ :u_unsuclog#660768767:u_unsuctty=tty1:\ :u_maxtries#3:chkent: This protected password database file is for the user perry . The user id for perry is 101. This value must match the /etc/passwd entry for this user.
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) 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 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, resolv.conf - 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.
resolver(4) resolver(4) 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) AUTHOR resolver was developed by the University of California, Berkeley. FILES /etc/resolv.conf Resolver configuration file. SEE ALSO named(1M), resolver(3N), gethostent(3N), hostname(5).
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.
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) sccsfile(4) Flags Keywords used internally (see admin(1) for more information on their use).
sccsfile(4) sccsfile(4) end @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).
sd(4) sd(4) (HP-UX Software Distributor) NAME sd - attributes and storage formats of objects that Software Distributor uses DESCRIPTION The SD commands create, install, distribute and manage software objects (bundles, products, subproducts and filesets). In addition, they define and manage other objects in support of the software administration tasks which users perform. This manual page describes the SD software object classes, their attributes, and the file formats used to store their definitions.
sd(4) sd(4) (HP-UX Software Distributor) fileset A grouping of one or more files contained in a product or sub-product. It groups a subset of a product’s files into a manageable unit. A fileset can also contain zero or more control_files. file The actual files that make up a fileset that get installed, configured, and removed. control_files The scripts developed by vendors to perform product- or fileset-specific operations during various software management tasks. Often called control_scripts.
sd(4) sd(4) (HP-UX Software Distributor) Depot Attributes Attribute copyright data_model_revision description dfiles layout_version mod_date Value Type multi_line_string revision_string multi_line_string tag_string revision_string one_line_string mod_time name_max number path_max pfiles tag title uuid contained bundles unsigned_integer unsigned_integer one_line_string unsigned_integer tag_string tag_string one_line_string one_line_string list of bundle objects list of product objects media object vendo
sd(4) sd(4) (HP-UX Software Distributor) uuid The depot’s Universal Unique Identifier (UUID). contained bundles The bundles available from the depot. contained products The products available from the depot. contained media The object defining the sequence number used to identify each medium. contained vendors The objects defining a vendor object that is associated with subsequent bundle and product objects that define a vendor_tag attribute.
sd(4) sd(4) (HP-UX Software Distributor) path The path to the root. root_type The type of root: shared, private or none. contained bundles The bundles installed into the root. contained products The products installed into the root. contained vendor The object defining a vendor object that is associated with subsequent bundle and product objects that define a vendor_tag attribute.
sd(4) sd(4) (HP-UX Software Distributor) revision Determines which category object definition to maintain in a depot when a definition being installed or copied does not match a definition already in the depot with the same category_tag . The category definition with the higher revision is maintained. Bundle and Product Attributes • Attributes marked with a + apply only to the product class. • Attributes marked with a - apply only to the bundle class.
sd(4) sd(4) (HP-UX Software Distributor) Attribute + all_filesets * architecture category_tag - contents control_directory copyright create_date create_time data_model_revision description directory install_date install_source install_type instance_id is_locatable is_patch layout_version * location machine_type mod_date mod_time number os_name os_release os_version + postkernel qualifier + readme * revision share_link size software_spec * tag title * vendor_tag + contained control scripts + contained files
sd(4) sd(4) (HP-UX Software Distributor) Like vendor_tag , this attribute associates this product or bundle with a category object containing additional information about the category (for example, a one-line title definition and a description of the category). contents The list of software_specs for a bundle. (Bundles can contain other bundles.) Fully qualified software specs at the fileset level are recommended when defining packages. (Applies to bundles only).
sd(4) sd(4) (HP-UX Software Distributor) os_release The operating system release(s) on which the product will run. os_version The operating system versions(s) on which the product will run. postkernel The path to a script that is run after kernel filesets are installed. qualifier A user-specified name that identifies a product or set of product versions. Can be set using swmodify and used in software_specs with other commands. readme The most recent information for the product.
sd(4) sd(4) (HP-UX Software Distributor) Subproduct Attributes Attribute contents description size software_spec tag title Value Type repeatable list of tag_string values multi_line_string unsigned_integer software_specification tag_string one_line_string Size 8K 64 256 Example commands data man commands data man "This subproduct ..." 14638872 Networking.Run,r=1.0 Manager Management Utilities contents A list of the filesets or subproducts that make up the subproduct.
sd(4) sd(4) (HP-UX Software Distributor) Attribute ancestor Size applied_patches Value Type repeatable list of software specs software_spec architecture one_line_string 64 category_tag control_directory corequisites tag_string path_string repeatable list of software_specs one_line_string 64 255 64 unsigned_integer revision_string 64 create_date create_time data_model_ revision description exrequisites install_date install_source instance_id is_kernel is_locatable is_packaged_ in_place is_patch
sd(4) sd(4) (HP-UX Software Distributor) supersedes software_spec tag title contained control scripts contained files tag_string one_line_string list of control script objects list of file objects 64 256 product.fileset, fr=revision commands Commands ancestor A list of filesets that will match the current fileset when installed on a target system if the match_target installation option is specified. Also determines the base to which a patch is applied.
sd(4) sd(4) (HP-UX Software Distributor) is_patch Identifies a software object as a patch. The default value is false . When set to true , a builtin category_tag attribute of value patch is automatically included. is_reboot Defines whether or not the fileset requires a reboot after install. is_secure Defines whether or not the fileset is encrypted on a CD-ROM media, requiring a codeword to install.
sd(4) sd(4) (HP-UX Software Distributor) prerequisites A list of dependencies on software that must be installed before this software can be installed. revision The revision (release number, version number) of the fileset. size The size of the fileset in bytes. state The current state of the fileset (resulting from the most recent operation performed on it). software_spec The full software specification for the fileset. Used to identify a unique fileset.
sd(4) sd(4) (HP-UX Software Distributor) File Attributes Attribute cksum compressed_cksum compressed_size compression_state compression_type gid group is_volatile link_source mode mtime owner path revision size source type uid Value Type unsigned_integer unsigned_integer unsigned_integer compression_enumeration tag_string unsigned_integer tag_string boolean path_string unsigned integer unsigned_integer tag_string path_string revision_string unsigned_integer path_string file_type_enumeration unsigned_inte
sd(4) sd(4) (HP-UX Software Distributor) source The full path to the source file for files which have been "packaged in place"; see swpackage(1M). type The type of file. uid The UID of the file’s owner. VALUE TYPES The value for each attribute must be of a specific type.
sd(4) sd(4) (HP-UX Software Distributor) result_enumeration Maximum length: none One of the following values: none error warning success revision_string Maximum length: 64 bytes Examples: 2.0, B.11.11 Revision strings contain zero or more dot-separated one_line_strings (above). software_specification Maximum length: none Examples: SD.agent or SD,r=2.0,a=HP-UX_B.11.11_32/64 Software specifications specify software in dependencies, ancestors and other attributes, as well as command line selections.
sd(4) sd(4) (HP-UX Software Distributor) SOFTWARE SPECIFICATION SYNTAX The SD commands and attributes support the following syntax for each software_specification: [,r revision][,a arch][,v vendor] [,c category ][,q= qualifier][,l= location] [,fr revision][,fa arch] • The = (equals) relational operator lets you specify selections with the following shell wildcard and pattern-matching notations: [ ], *, ? For example, *man selects all bundles and products with tags that end
sd(4) sd(4) (HP-UX Software Distributor) HOST OBJECT FORMAT The file /var/adm/sw/host_object defines the software depots on the local host which have been registered with the swagentd daemon running on the host. The file has this format: host data_model_revision distribution path directory 2.40 Defines a contained (registered) depot distribution path directory ...
sd(4) sd(4) (HP-UX Software Distributor) tag[.instance_id] The tag component is the product or fileset tag attribute. If more than one product with the same tag exists in the software depot, the instance_id component is necessary. This component is the product or fileset instance_id attribute. On a short-filename filesystem, the tag component is truncated to the first 9 characters (if necessary).
sd(4) sd(4) (HP-UX Software Distributor) INDEX FORMAT An INDEX file describes all of the attributes (except for contained scripts and contained files) of a fileset, product, depot, or root. In a depot, the fileset, product, and depot INDEX files are concatenated together to form the catalog/INDEX file. In a root, the fileset, product, and root INDEX files are concatenated together to form the var/adm/sw/products/INDEX file. This section describes the keyword syntax used in an INDEX file.
sd(4) sd(4) (HP-UX Software Distributor) Bundle or Product INDEX Format NOTE: • The tag attribute is always required for all objects. • The contents attribute is required for subproducts and bundles . • Keywords marked with a + apply only to product INDEX format. • Keywords marked with a - apply only to bundle INDEX format.
sd(4) sd(4) (HP-UX Software Distributor) subproduct tag contents description size software_spec title tag_value contents_value description_value size_value software_specification_value title_value Fileset INDEX Format NOTE: • The tag attribute is always required. • The media_sequence_number attribute is required for filesets within a multiple tape distribution. • Multiple definitions of ancestor , corequisites , exrequisites quisites are allowed.
sd(4) sd(4) (HP-UX Software Distributor) INFO FORMAT An INFO file describes all of the control scripts and other files contained within a fileset or product. This section describes the keyword syntax used in an INFO file. Control File Format control_file tag interpreter path result tag_value interpreter_value path_value result_value The path , and tag attributes are required.
sd(4) sd(4) (HP-UX Software Distributor) LOCKING These commands use a common locking mechanism for reading and modifying both root directories and software depots. This mechanism allows multiple readers but only one writer on a root or depot. The commands which modify software in an (alternate) root directory are restricted from simultaneous modification using fcntl(2) locking on the file /var/adm/sw/products/swlock relative to the root directory (e.g. /var/adm/sw/products/swlock).
securenets(4) securenets(4) NAME securenets - 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) against the number of most recently used passwords stored in password history for a particular user. A user is not allowed to re-use a previously used password. PASSWORD_HISTORY_DEPTH=N A new password is checked against only the N most recently used passwords for a particular user. A configuration of password history depth of 2 prevents users from alternating between two passwords.
security(4) security(4) passwd -w option can be used to override this value for a specific user. PASSWORD_WARNDAYS=N Users are warned N days before their password expires. Default value: PASSWORD_WARNDAYS=0 (no warning) RSH_SECURITY This parameter controls how login filters environment variables passed to restricted shells, for example, rksh . Note: This parameter is supported by login patch PHCO_23900 or later. RSH_SECURITY=0 All variables except SHELL and PATH can be set.
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 IDs DESCRIPTION The file /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(1) , useradd(1m) , usermod(1m) , and userdel(1M) 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
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).
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(1M) (purchased with the OpenView product). The SNMP agent operates correctly if no values are configured in /etc/SnmpAgent.d/snmpd.conf. /etc/SnmpAgent.d/snmpd.
snmpd.conf(4) snmpd.conf(4) as for the get-community-name: above. Separate the fields by blanks or tabs. A # character indicates the beginning of a comment; characters from the # character to the end of the line are ignored. EXAMPLES Each line in the following example snmpd.conf file is preceded by a comment (beginning with #) that explains the entry. Please note that this is an example. Taken as a whole in is not intended to represent a configuration that you should use.
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) enable count Selecting this softkey will enable count softkey nodes to the right of this one - default is 0. {filter command } This node is only active for filters or commands, respectively - default is either. {motorola precision } This node is only active when keysh is running on a Motorola (MC680x0) or precision (PA-RISC) processor, respectively - default is either. This node starts out disabled and must be enabled to be used - default is to start out enabled.
softkeys(4) • softkeys(4) a word allocation statement.
softkeys(4) word[ number ]*= number word[ number ]/= number word[ number ]%= number word[ number 1]&= string softkeys(4) 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 . . . } Where the else part is optional. If number is non-zero, the first block of edit statements is executed.
softkeys(4) softkeys(4) string.
swpackage(4) swpackage(4) (HP-UX Software Distributor) NAME swpackage - product specification file (PSF) format DESCRIPTION Introduction The swpackage command packages software into: • a distribution directory (which can be accessed directly or copied onto a CD-ROM), • a distribution tape, such as DDS, nine-track or cartridge tapes. Both directory and tape distributions use the same format. SD can read both tar and cpio tape depots. See sd(4) for details on tape format.
swpackage(4) swpackage(4) (HP-UX Software Distributor) PRODUCT SPECIFICATION FILE SYNTAX A PSF is structured as follows: [] [] [] [] ... [] [] [] [] ... [] [] ...
swpackage(4) swpackage(4) (HP-UX Software Distributor) • Use double quotes (") to define values that span multiple lines: "This is an example of a two-line value." • Double quotes (") are optional when defining a value that contains embedded whitespace. Attribute Table The following tables summarize the objects and attributes which can be defined in a PSF.
swpackage(4) swpackage(4) (HP-UX Software Distributor) Attribute Table (continued) Keyword product * tag * architecture category_tag contents copyright description directory is_locatable is_patch layout_version machine_type number os_name os_release os_version postkernel readme revision title * vendor_tag control_files end subproduct tag contents description title end Type Size Example tag_string one_line_string 64 64 one_line_string repeatable list multi_line_string multi_line_string path_string bo
swpackage(4) swpackage(4) (HP-UX Software Distributor) Attribute Table (continued) Keyword fileset * tag ancestor Type Size Example 64 architecture tag_string repeatable list of product.fileset one_line_string category_tag corequisites description dynamic_module exrequisite is_kernel is_locatable is_patch is_reboot is_sparse machine_type tag_string software_spec multi_line_string one_line_string software_spec boolean boolean boolean boolean boolean uname_string commands product.
swpackage(4) swpackage(4) (HP-UX Software Distributor) The keyword is a filename character string. The value associated with a keyword is processed as an attribute_value. It can be continued across multiple input lines or can reference a file containing the value for the keyword. Vendor-defined attributes are noted during packaging or when modified with swmodify . These attributes can be listed with swlist . As always, use caution in constructing your Product Specification File.
swpackage(4) swpackage(4) (HP-UX Software Distributor) Examples: /mfg/sd/files/usr = /usr A value of the form: ‘‘source [=destination ]’’ where the source defines the directory in which subsequently defined files are located. The optional destination maps the source to a destination directory in which the files will actually be installed.
swpackage(4) swpackage(4) (HP-UX Software Distributor) • • fr and fa apply only to filesets. r , a , v , c , and l apply only to bundles and products. They are applied to the leftmost bundle or product in a software specification. • The (relational operator) component can be of the form: ==, >=, <=, <, >, or != which performs individual comparisons on dot-separated fields. For example, r>=B.10.00 chooses all revisions greater than or equal to B.10.00 .
swpackage(4) swpackage(4) (HP-UX Software Distributor) layout_version Defines the semantics to use when parsing the PSF. To ensure IEEE Standard 1387.2 semantics, define a layout_version of 1.0 , as the first attribute. tag Defines the identifier (short name) for the distribution depot or tape. copyright Defines the copyright information for the distribution depot or tape; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
swpackage(4) swpackage(4) (HP-UX Software Distributor) description revision end category Keyword that begins the category specification. tag Defines the identifier (short name) for the category. title Defines the full name (one line description) for the category. description A more detailed description of the category.
swpackage(4) swpackage(4) (HP-UX Software Distributor) tag architecture category_tag contents copyright description directory is_locatable is_patch layout_version machine_type number os_name os_release os_version postkernel readme revision title vendor_tag SD HP-UX_B.11.11_32/64 Ordered Apps prod.fs1.r=1.0,a=,v=
swpackage(4) swpackage(4) (HP-UX Software Distributor) each bundle specified, swpackage requires the bundle , tag , and contents keywords. product Required keyword that begins the product specification. tag Defines the identifier (short name) for the product or bundle. architecture Describes the target system(s) on which the product or bundle will run. Provides a humanreadable summary of the four uname(1) attributes which define the exact target system(s) the product supports.
swpackage(4) swpackage(4) (HP-UX Software Distributor) os_name Defines the operating system(s) on which the product will run. (If not specified, swpackage assigns a value of "*", meaning the product runs on all operating systems.) If there are multiple operating systems, use wildcards or use the ’|’ character to separate them. This attribute should pattern match to the value of uname -s [: getconf KERNEL_BITS] on the supported target system(s).
swpackage(4) swpackage(4) (HP-UX Software Distributor) description Defines the multi-paragraph description of the subproduct; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text. title Defines the full name (one-line description) of the subproduct. end Ends the subproduct specification. This keyword is optional.
swpackage(4) swpackage(4) (HP-UX Software Distributor) You can define additional disk space requirements for the fileset using a space control_file. (See the "Control Script Specification" section for more information.) fileset Keyword that begins fileset specification. tag Defines the identifier (short name) for the fileset. architecture Describes the target system(s) on which the fileset will run if filesets for multiple architecture are included in a single product.
swpackage(4) swpackage(4) (HP-UX Software Distributor) false. machine_type Defines the machine(s) on which the files will run if a fileset architecture has been defined. (If not specified, swpackage assigns a value of "*", meaning the files run on all machines.) If there are multiple machine platforms, use wildcards or use the ’|’ character to separate them. This attribute should pattern match the output of the model command on the supported target machine(s).
swpackage(4) swpackage(4) (HP-UX Software Distributor) Each keyword/value defines a dependency relationship on another software object. The object can be within the same product as the dependent fileset, or it can be within another product. Multiple dependency specifications are allowed. You can use them to define AND relationships between the dependencies. (The AND relationship is implied because all dependencies must be satisfied.) You can also define OR relationships using the ’|’ character.
swpackage(4) swpackage(4) (HP-UX Software Distributor) checkinstall checkremove control_file control_file scripts/myscript common scripts/myscript common scripts/myscript=preinstall common scripts/myscript=configure common SD supports the following types of control scripts: checkinstall Defines the installation check script executed by swinstall . This script is executed during the analysis of each target, and it checks that the installation can be attempted.
swpackage(4) swpackage(4) (HP-UX Software Distributor) supported for filesets only. It should undo the steps taken by the postinstall script. unpreinstall Defines the installation post-restore script executed by swinstall . A fileset script is executed immediately after the fileset files are restored if there is an error and the autorecover_product option is set to true. A product script is executed after all filesets for that product have been restored.
swpackage(4) swpackage(4) (HP-UX Software Distributor) the product files are located. SW_PATH A PATH variable which defines a minimum set of commands available for use in a control script (e.g. /sbin:/usr/bin). SW_ROOT_DIRECTORY Defines the root directory in which the session is operating, either / or an alternate root directory. This variable tells control scripts the root directory in which the products are installed.
swpackage(4) swpackage(4) (HP-UX Software Distributor) The destination directory must be an absolute pathname. The directory keyword is optional. Recursive File Specification The file * keyword directs swpackage to recursively include every file (and directory) within the current source directory in the fileset. (Partial wildcarding is not supported—e.g., file dm* to indicate all files starting with "dm".
swpackage(4) swpackage(4) (HP-UX Software Distributor) -g [group[,]][ gid] Defines the destination file’s group name and/or or gid. If only the group is specified, the group and gid attributes are set for the destination file object, based on the packaging host’s /etc/group . If only the group is specified, and it contains digits only, it is interpreted as the gid, and is set as the gid attribute for the destination object; no group name is assigned to the object.
swpackage(4) swpackage(4) (HP-UX Software Distributor) If the filename specifies a directory, then all files below that directory are excluded. Include files let you include file definitions from a separate file. The syntax is: file < include_file The include file must be separated from the file keyword by a less than sign (<). EXAMPLES This example illustrates a typical PSF. # PSF file which defines an example product. depot layout_version 1.
swpackage(4) swpackage(4) (HP-UX Software Distributor) s # Fileset definitions: fileset tag commands title SD Commands (management utilities) revision 2.42 description < data/descr.commands # Dependencies corequisites SD.data corequisites SD.agent # Control files: configure scripts/configure.commands # Files: directory ./commands=/usr/sbin file swinstall file swcopy ... directory ./nls=/usr/lib/nls/C file swinstall.cat file swpackage.cat directory ./ui=/usr/lib/sw/ui file * ... end # commands ...
swpackage(4) swpackage(4) (HP-UX Software Distributor) Explicitly list files and directories, no directory mapping specified: file ./commands/swinstall /usr/sbin/swinstall ... file ./nls /usr/lib/nls/C file ./nls/swinstall.cat /usr/lib/nls/C/swinstall.cat Use all specification types to include files: directory ./commands=/usr/sbin file * directory ./nls=/usr/lib/nls/C file swinstall.cat ... file ./obam/obam.dm /etc/interface.lib/obam/obam.dm Redefine specific files previously defined using file * (e.g.
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 ..
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)
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=
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 tilde_glitch transparent_underline xon_xoff eslok hz ul xon Escape can be used on the status line Hazeltine; can’t print tilde (˜) Underline character overstrikes Terminal uses xon/xoff handshaking es hz ul xo Numbers Variable Capname Termcap Code Description bit_image_entwining bit_image_type buffer_capacity columns dot_horz_spacing dot_vert_spacing init_tabs label_height label_width lines lines_of_memory max_attributes magic_cookie_glitch max_colors max_mic
term_c(4) t term_c(4) change_scroll_region char_padding char_set_names clear_all_tabs clear_margins clear_screen clr_bol clr_eol clr_eos code_set_init color_names column_address command_character cursor_address cursor_down cursor_home cursor_invisible cursor_left cursor_mem_address cursor_normal cursor_right cursor_to_ll cursor_up cursor_visible define_bit_image_region define_char delete_character delete_line device_type dis_status_line display_pc_char down_half_line ena_acs end_bit_image_region enter_al
term_c(4) enter_shadow_mode enter_standout_mode enter_subscript_mode enter_superscript_mode enter_top_hl_mode enter_underline_mode enter_upward_mode enter_vertical_hl_mode enter_xon_mode erase_chars exit_alt_charset_mode exit_am_mode exit_attribute_mode exit_ca_mode exit_delete_mode exit_doublewide_mode exit_insert_mode exit_italics_mode exit_leftward_mode exit_micro_mode exit_pc_charset_mode exit_scancode_mode exit_shadow_mode exit_standout_mode exit_subscript_mode exit_superscript_mode exit_underline_mod
term_c(4) t key_cancel key_catab key_clear key_close key_command key_copy key_create key_ctab key_dc key_dl key_down key_eic key_end key_enter key_eol key_eos key_exit key_f0 key_f1 key_f2 key_f3 key_f4 key_f5 key_f6 key_f7 key_f8 key_f9 key_f10 key_f11 key_f12 key_f13 key_f14 key_f15 key_f16 key_f17 key_f18 key_f19 key_f20 key_f21 key_f22 key_f23 key_f24 key_f25 key_f26 key_f27 key_f28 key_f29 key_f30 key_f31 key_f32 key_f33 key_f34 key_f35 key_f36 key_f37 key_f38 key_f39 key_f40 Section 4−−322 term_c(
term_c(4) key_f41 key_f42 key_f43 key_f44 key_f45 key_f46 key_f47 key_f48 key_f49 key_f50 key_f51 key_f52 key_f53 key_f54 key_f55 key_f56 key_f57 key_f58 key_f59 key_f60 key_f61 key_f62 key_f63 key_find key_help key_home key_ic key_il key_left key_ll key_mark 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 ke
term_c(4) t term_c(4) 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 key_sright key_srsume key_ssave key_ssuspend key_stab key_sundo key_suspend key_undo key_up keypad_local keypad_xmit lab_f0 lab_f1 lab_f2 lab_f3 lab_f4 lab_f5 lab_f6 lab_f7 lab_f8 lab_f9 lab_f10 label_format label_off label_on meta_off meta_on micro_column_address micro_down micro_left micro_right micro_row_add
term_c(4) 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 parm_up_micro pc_term_options pkey_key pkey_local pkey_plab pkey_xmit plab_norm print_screen prtr_non prtr_off prtr_on pulse quick_dial remove_clock repeat_char req_for_input req_mouse_pos reset_1string reset_2string reset_3string reset_file restore_cursor row_address save_cursor scancode_escape scroll_forward scroll_reverse select_ch
term_c(4) term_c(4) set_right_margin_parm set_tab set_tb_margin set_top_margin set_top_margin_parm set_window start_bit_image start_char_set_def stop_bit_image stop_char_set_def subscript_characters superscript_characters tab these_cause_cr to_status_line tone user0 user1 user2 user3 user4 user5 user6 user7 user8 user9 underline_char up_half_line wait_tone xoff_character xon_character zero_motion smgrp hts smgtb smgt smgtp wind sbim scsd rbim rcsd subcs supcs ht docr tsl tone u0 u1 u2 U3 u4 u5 u6 u7 u8 u
terminfo(4) terminfo(4) (ENHANCED CURSES) NAME terminfo - printer, terminal, and modem capability database SYNOPSIS /usr/lib/terminfo/?/* List of Section Headings in DESCRIPTION Terminfo Source Format Source File Syntax Minimum Guaranteed Limits Formal Grammar Defined Capabilities Sample Entry Types of Capabilities in the Sample Entry Device Capabilities Insert/Delete Line Printer Capabilities Capabilities that Cause Movement Alternate Character Sets Dot-Matrix Graphics Effect of Changing Printing Resolu
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) 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 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 number_
terminfo(4) terminfo(4) (ENHANCED CURSES) Strings t 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_e
terminfo(4) terminfo(4) (ENHANCED CURSES) 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 enter_stand
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) 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 key_srig
terminfo(4) terminfo(4) (ENHANCED CURSES) t 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_cur
terminfo(4) terminfo(4) (ENHANCED CURSES) 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 r1 r2 r3 rf rc cv sc S7 sf sr Zj s0 s1
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 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 u9 uc hu WA XF XN Zx 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 C-language 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) audible signal (such as a bell or a beep), specify it as bel. If, like most devices, the device 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.
terminfo(4) terminfo(4) (ENHANCED CURSES) %P[a-z] Set dynamic variable [a-z] to pop(). %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) than the more general two-argument sequence (as with the Hewlett-Packard 2645) and can be used in preference to cup. If there are argumentised local motions (such as "move n spaces to the right"), 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.
terminfo(4) terminfo(4) (ENHANCED CURSES) While these are two logically separate attributes (one line versus multiline insert mode, and special treatment of untyped spaces) we have seen no terminals whose insert mode cannot be described with the 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.
terminfo(4) terminfo(4) (ENHANCED CURSES) line or the cursor is addressed. Programs using standout mode should exit standout mode before moving the cursor or sending a newline, unless the msgr capability, asserting that it is safe to move in standout 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.
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) 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 (halfline down). This is primarily useful for superscripts and subscripts on hardcopy terminals.
terminfo(4) terminfo(4) (ENHANCED CURSES) "magic cookie". Therefore, to erase standout mode, it is necessary, instead, to use delete and insert line. For Beehive Superbee terminals that do not transmit the escape or control-C characters, specify xsb, indicating that the f1 key is to be used for escape and the f2 key for control-C. Similar Terminals If there are two similar terminals, one can be defined as being just like the other with certain exceptions.
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) or formfeed, are used. The other is used for the capability of suspending the motion that normally occurs after printing a character. Miscellaneous Motion Strings docr List of control characters causing cr zerom Prevent auto motion after printing next single character Margins terminfo provides two strings for setting margins on terminals: one for the left and one for the right margin.
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) Applications that use these values should recognize the variability in the print rate. Straight text, in short lines, with no embedded control sequences will probably print at close to the advertised print rate and probably faster than the rate in cps. Graphics data with a lot of control sequences, or very long lines of text, will print at well below the advertised rate and below the rate in cps.
terminfo(4) terminfo(4) (ENHANCED CURSES) 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. COLUMNS Specifies column information that can override the column information in terminfo. See the "Selecting a Terminal" section. LINES Specifies lines information that can override the lines information in terminfo. See the "Selecting a Terminal" section.
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/ .
tun(4) tun(4) NAME tun - IP network tunnel driver SYNOPSIS #include open("/dev/tunn", mode); DESCRIPTION When IP packets are written to /dev/tun n or /dev/tun n+M, they will be received by the kernel’s IP layer on the network interface dun. When the kernel’s IP layer sends packets to the IP interface du n, they will be available for reading on /dev/tun n or /dev/tun n+M.
tun(4) tun(4) TUIOGNAME FIONBIO Get the interface name. Set or clear non-blocking mode for I/O operations. EXAMPLES #include int tun_fd = -1, len; char *packet; tun_fd = open("/dev/tun0", O_RDWR); ioctl(tun_fd, TUIOSNAME, "du"); len = read(tun_fd, packet, size); write(tun_fd, packet, len); ERRORS If a packet is delivered to the interface for an address family other than AF_INET , EAFNOSUPPORT will be returned.
tunefstab(4) tunefstab(4) NAME tunefstab (vxfs) - VxFS 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) 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) 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), getut(3C). STANDARDS CONFORMANCE
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.
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 mail.aliases mail.byaddr ethers.byaddr ethers.byname group.bygid group.byname 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 Abbreviated Mapname mail.alias mail.byad ether.byad ether.byna group.bygi group.byna hosts.byad hosts.byna netgroup netgr.
ypfiles(4) ypfiles(4) General NIS Mapname ASCII Source aliases /etc/mail/aliase ethers ∗ ∗ group /etc/group hosts /etc/hosts netgroup /etc/netgroup netid networks /etc/netid /etc/networks passwd /etc/passwd protocols /etc/protocols publickey rpc /etc/publickey /etc/rpc services /etc/services automounter ypservers /etc/auto_master ∗∗∗ Standard NIS Mapname mail.aliases mail.byaddr ethers.byaddr ethers.byname group.byname group.bygid hosts.byname hosts.byaddr netgroup netgroup.
(Notes) (Notes) y Section 4−−378 Hewlett-Packard Company −1− HP-UX 11i Version 1: September 2005
