HP-UX Reference Section 4: File Formats HP-UX 11i Version 3 Volume 8 of 10 Manufacturing Part Number : B2355-91024 E0207 Printed in USA © Copyright 1983-2007 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.
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.
Typographical Conventions audit (5) An HP-UX manpage reference. For example, 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 hyperlink 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 hyperlink to the book itself.
Command Syntax Literal A word or character that you enter literally. Replaceable A word or phrase that you replace with an appropriate value. -chars One or more grouped command options, such as -ikx. The chars are usually a string of literal characters that each represent a specific option. For example, the entry -ikx is equivalent to the individual options -i, -k, and -x. The plus character (+) is sometimes used as an option prefix. -word A single command option, such as -help.
Function Synopsis and Syntax HP-UX functions are described in a definition format rather than a usage format. The definition format includes type information that is omitted when the function call is actually included in a program. The function syntax elements are the same as for commands, except for the options; see “Command Syntax” on page 7. Function General Definition The general definition form is: type func ( type param [ , type param ]...
Revision History Part Number Release; Date; Format; Distribution B2355-60130 HP-UX 11i Version 3; February 2007; one volume HTML; http://docs.hp.com and Instant Information. B2355-91017-26 HP-UX 11i Version 3; February 2007; ten volumes PDF; http://docs.hp.com, Instant Information and print. B2355-60127 HP-UX 11i Version 1; September 2005 Update; one volume HTML; http://docs.hp.com and Instant Information. B2355-90902-11 HP-UX 11i Version 1; September 2005 Update; ten volumes PDF; http://docs.hp.
Volume Eight Table of Contents Section 4
Volume Eight Table of Contents Section 4
Table of Contents Volume Eight Section 4: File Formats Entry Name(Section): name Description intro(4): intro ....................................................................................................... introduction to file formats .rhosts: security files authorizing access by remote hosts and users on local host ............. see hosts.equiv(4) password file format .......................................................................................................
Table of Contents Volume Eight Entry Name(Section): name Description ftpservers(4): ftpservers ................................................. ftpd virtual hosting configuration specification file ftpusers(4): ftpusers ..................................................................................................... security file for ftpd gated.conf(4): gated.conf ......................................................................... GateDaemon Configuration Guide gettydefs(4): gettydefs ...........
Table of Contents Volume Eight Entry Name(Section): name Description privgrp(4): privgrp() ........................................................................................... format of privileged values profile(4): profile ............................................................................. set up user’s environment at login time proto(4): proto ............................................................................................................
Notes 16 Hewlett-Packard Company HP-UX 11i Version 3: February 2007
Section 4 File Formats
Section 4 File Formats
intro(4) intro(4) NAME intro - introduction to file formats DESCRIPTION This section outlines the formats of various files. The C struct declarations for the file formats are given where applicable. Usually, these structures can be found in directories /usr/include or /usr/include/sys. SEE ALSO hier(5), introduction(9). Web access to HP-UX documentation at http://docs.hp.com.
a.out(4) a.out(4) NAME a.out - assembler and link editor output SYNOPSIS #include (for ELF files) #include (for SOM files) a 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.out(4) In a relocatable file, initialized code and data often contain references to locations elsewhere in the file, and to unresolved symbols defined in other files. These references are patched at link time using the relocation information. Each entry in the relocation information (a "fixup") specifies a location within the initialized data for a subspace, and an expression that defines the actual value that should be placed at that location, relative to one or two symbols.
a.out(4) a.out(4) struct sys_clock { unsigned int secs; unsigned int nanosecs; }; Auxiliary Headers The auxiliary headers are contained in a single contiguous area in the file, and are located by a pointer in the file header. Auxiliary headers are used for two purposes: to attach users’ version and copyright strings to an object file, and to contain the information needed to load an executable program. In an executable program, the HP-UX auxiliary header must precede all other auxiliary headers.
a.out(4) a.
a.out(4) 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.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) #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.
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. Accounting files are currently written in 32-bit format. Thus, 64-bit applications which read the files need to make special provisions. In particular, the acct.h header declares the ac_btime field as int32_t rather than a time_t in 64-bit compilations.
acps.conf(4) acps.conf(4) NAME acps.conf - configuration file for the Access Control Policy Switch (ACPS) SYNOPSIS a /etc/acps.conf DESCRIPTION The ACPS configuration file controls which modules are consulted for making an access control decision, the order in which the modules are consulted, and the rules for combining their responses to return a result back to the application. Syntax and Default Behavior The acps.
acps.conf(4) acps.conf(4) # If custom rule does not match, use default local RBAC # rule processing HP-UX RBAC : libacpm_hpux_rbac : : SEE ALSO acps(3), acps_api(3), acps_spi(3).
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 | .
audeventstab(4) audeventstab(4) NAME audeventstab - define and describe audit system events a 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 - audit trail format and other information for auditing 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 sequence number, process ID, event type, and record body length.
audit.conf(4) audit.conf(4) NAME audit.conf, audit_site.conf - files containing event mapping information and site-specific event mapping information a DESCRIPTION Files /etc/audit/audit.conf and /etc/audit/audit_site.conf store the event mapping information that can be used by audevent and audisp . An event is a particular system operation. It may be either a self-auditing event or a system call. Auditable events are classified into several event categories and/or profiles.
audit.conf(4) audit.conf(4) .set_sys_info() by the auditing system. The interface of .set_sys_info() is not publicly exported, but the security relevant information of this system call is described in /etc/audit/audit.info; this file documents the security relevant information for all system calls that have names beginning with a period (.). Profiles are defined using the PROFILE directive. Profiles can be combinations of any events. In /etc/audit/audit_site.
authcap(4) authcap(4) (TO BE OBSOLETED) 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 manpages. This manpage describes the format of these databases, and describes the philosophy of conversion into data structures.
authcap(4) authcap(4) (TO BE OBSOLETED) where num is a decimal or (0-preceded) octal number. Boolean capabilities have the format: id or id@ where the first form signals the presence of the capability and the second form signals the absence of the capability. String capabilities have the format: id=string where string is 0 or more characters. The \ and : characters are escaped as \\ and \: respectively.
autofs(4) autofs(4) NAME autofs - file containing parameter values for the automountd daemon and the automount command SYNOPSIS a /etc/default/autofs DESCRIPTION The autofs file resides in directory /etc/default and supplies default parameters for the automountd daemon and the automount command. The autofs file format is ASCII; comment lines begin with the crosshatch (#) character. Parameters consist of a keyword followed by an equal sign followed by the parameter value.
bootconf(4) bootconf(4) NAME bootconf - boot device configuration table DESCRIPTION The /stand/bootconf file 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) bootconf(4) FILES /stand/bootconf SEE ALSO mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). Software Distributor documentation.
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. 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. However, the cdnode data structure does not reside on the physical media, but instead is kept in kernel memory space only.
cdrom(4) cdrom(4) NAME cdrom - CD-ROM background information DESCRIPTION This manpage provides general information on existing CD-ROM standards, terminology, data layout, and levels of support. More detailed information is available in the standard documents listed in SEE ALSO. Not all topics discussed here are supported in the current HP-UX release. Refer to the DEPENDENCIES section for details about the contents of the current release.
cdrom(4) cdrom(4) 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 four 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. Unicode An escape character followed by a u, followed by four or five hexadecimal digits.
charmap(4) charmap(4) demonstrate flexibility. The keyword WIDTH_DEFAULT could have been added as appropriate. SEE ALSO eucset(1), localedef(1M), localedef(4). STANDARDS CONFORMANCE localedef : POSIX.2, XPG4, UNIX 2003.
compartments(4) compartments(4) NAME compartments - HP-UX compartments files DESCRIPTION HP-UX compartments are defined by creating one or more ASCII files in the /etc/cmpt directory. Only file names ending with .rules are parsed for compartment definitions. Collectively, these files define compartments and compartment access rules for local system objects. System objects that have compartment access controls defined include file system objects, inter-process communication objects, and network objects.
compartments(4) compartments(4) permission Sets the permissions allowed for processes in this compartment to access the file_object in the way specified. none Denies any access to the file_object for any process in this compartment. If specified, none of the other possible arguments can be used. all Indicates all permissions on file_object. all is an alias for the expression nsearch , read , write , unlink , create . nsearch Controls search access to the file_object.
compartments(4) compartments(4) access. Rules of this type can be either subject-centric or object-centric. Two formats are available for IPC rules. The first form of IPC rules controls process communication and uses the following format: (grant |access ) (pty |fifo |uxsock |ipc ) compartment_name where the values are defined as follows: grant Allows processes in the compartment compartment_name to access the specified IPC mechanism in this compartment. This keyword specifies an object-centric rule.
compartments(4) compartments(4) communications, the subject and target compartments should be of the processes that are communicating and not that of the interface being used for communication. Each rule is specified by protocol (TCP, UDP, or any raw protocol number) and the target compartment, and can optionally filter based on local or peer port numbers (TCP and UDP only). If an explicit rule does not match a communication attempt, the default is to deny communication.
compartments(4) • • compartments(4) Privilege limitation rules Network interface rules Privilege Limitation Rules Privilege limitations provide a fine control of privileges that cannot be obtained by the processes in a compartment when calling execve() . See execve (2). Privilege limitation rules use the following format: disallowed privileges privilege[,privilege...] where the values are define as follows: c disallowed privileges Identifies this as a privilege limitation. privilege[,privilege...
compartments(4) compartments(4) Interface lan0 is assigned to compartment LAN0, IP address range 192.168.0.0/16 is assigned to compartment IP_16, IP address range 192.0.0.0/8 is assigned to compartment IP_8, and IP address 192.168.0.0 is assigned to compartment IP. Note that IPv4 address 192.168.0.0 belongs to all these ranges specified in the rules for IP_8, IP_16, and IP. If the interface lan0 is assigned an address of 192.168.0.0, there is an additional conflict.
compartments(4) compartments(4) FILES The only rules files not described here that affect the compartment rules on a system are those included through an #include directive. The /etc/cmpt directory is used as the default search path for #include directives that use relative paths. /etc/cmpt/ The human-readable version of the compartment rules. All files whose names end in *.rules that reside in the /etc/cmpt directory or its sub-directories are processed when setting rules. /etc/cmpt-rules.
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) (TO BE OBSOLETED) 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) (TO BE OBSOLETED) 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) (TO BE OBSOLETED) NAME devassign - device assignment database file for a trusted system SYNOPSIS /tcb/files/devassign DESCRIPTION The system supports a single device assignment database that contains entries for local login terminals. The format of the terminal control database file is identical to other trusted system authentication database files. For more information on the file format, see authcap(4).
dfstab(4) dfstab(4) NAME dfstab - file containing commands for sharing resources across a network DESCRIPTION dfstab resides in the directory /etc/dfs and contains commands for sharing resources across a network. dfstab gives a system administrator a uniform method for controlling the automatic sharing of local resources. Each line of the dfstab file consists of a share(1M) command. The dfstab file can be read by the shell to share all resources. The shareall command reads dfstab to share all resources.
dialups(4) dialups(4) NAME dialups, d_passwd - dialup security control DESCRIPTION dialups and d_passwd are used to control the dialup security feature of login (see login(1)). If /etc/dialups is present, the first word on each line is compared with the name of the line upon which the login is being performed (including the /dev/ , as returned by ttyname() (see ttyname(3C)). If the login is occurring on a line found in dialups , dialup security is invoked. Anything after a space or tab is ignored.
dir(4) dir(4) NAME dir - format of directories on short-name HFS file systems SYNOPSIS #include #include Remarks This entry describes the System V-compatible directory format for the HFS file system. It is provided strictly for backward compatibility and compatibility with applications expecting a System V file system environment. It is not compatible with the similar but more general HFS directory format in
disktab(4) disktab(4) NAME disktab - disk description file SYNOPSIS #include DESCRIPTION disktab is a simple database that describes disk geometries. Entries in disktab consist of a number of colon-separated fields. The first entry for each disk gives the names by which the disk is known, separated by vertical bar (|) characters. This file is provided for backward compatibility with previous HP-UX releases only. Its use is discouraged.
dlpi(4) dlpi(4) NAME dlpi.h - data link provider interface standard header file SYNOPSIS /usr/include/sys/dlpi.h DESCRIPTION is the standard header file containing DLPI requests as prescribed by the DLPI 2.0 standard. It contains the definitions for the primitives, acknowledgements and associated structures. The header file must be included by all DLS users (user-space and kernel-space) who intend to interact with LAN drivers through DLPI.
dlpi_drv(4) dlpi_drv(4) NAME dlpi_drv.h - definitions of interfaces for device drivers to interact with DLPI SYNOPSIS /usr/include/sio/dlpi_drv.h DESCRIPTION The header file contains definitions of structures and function prototypes that are required by networking device drivers to interact with DLPI (data link provider interface). The header file contains interfaces that could be used by tightly coupled and loosely coupled drivers.
dlpi_ext(4) dlpi_ext(4) NAME dlpi_ext.h - HP-specific extensions for DLPI SYNOPSIS /usr/include/sys/dlpi_ext.h DESCRIPTION is the header file for HP-specific extensions to data link provider interface, DLPI 2.0 standard. The header file contains definitions for primitives, acknowledgements, ioctls and associated structures to satisfy needs of DLS users over and beyond what is provided by DLPI 2.0 standard.
dosif(4) dosif(4) NAME DOSIF - DOS interchange format DESCRIPTION The DOS Interchange Format (DOSIF) 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. Use the dos2ux and ux2dos commands to convert files between HP-UX and DOS file formats; see dos2ux(1). 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).
efi(4) efi(4) (Itanium(R)-Based Processor Family Only) NAME efi - Extensible Firmware Interface description DESCRIPTION The EFI (Extensible Firmware Interface) is an interface between HP-UX and the Itanium-based platform firmware. The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI encompasses the use of FAT-32 for a system partition, and FAT-12 or FAT-16 for removable media. The system partition is required on a bootable disk for the Itanium-based platform.
evm.auth(4) evm.auth(4) NAME evm.auth - EVM authorization file SYNOPSIS event_rights { class event_class post rights_list access rights_list } service_rights { service service_name execute rights_list } e DESCRIPTION Authorization is control of the right to post, subscribe to, or retrieve an EVM event, or to execute services defined in the EVM daemon configuration file. The evm.auth file is a text file that controls event authorization.
evm.auth(4) evm.auth(4) The keywords described may be entered in a case-insensitive manner. The allowable strings and the minimum number of characters is shown in the following table. A minimum of zero (0) indicates that all characters are required. Keyword access class event_rights execute post service service_rights Minimum 0 0 7 4 0 4 9 Notes 1. If you add an event_rights entry to the authorization file, you must make sure there is a corresponding base event template in the template file library.
evmchannel.conf(4) evmchannel.conf(4) NAME evmchannel.conf - EVM channel configuration file SYNOPSIS path ch_path cleanup_time [[hh:]mm:]ss channel { name path events fn_get fn_details fn_explain fn_monitor fn_cleanup mon_period } ch_name ch_path evt_class get_function [arguments ] details_function [arguments ] explain_function monitor_function [arguments ] cleanup_function monitor_period e DESCRIPTION The term event channel describes any facility used to publish or retrieve event information.
evmchannel.conf(4) evmchannel.conf(4) name ch_name Specifies a name to be associated with the event channel. The name can include any printable character. events evt_class The class of events associated with this channel. The evt_class is a dot delimited field with the same syntax as an event name . When evmshow is run with the -d or -x option, it must find an event channel matching each event it receives, so that it can determine which channel function to run.
evmchannel.conf(4) evmchannel.conf(4) fn_monitor monitor_function [arguments ] The monitor function provides a mechanism for monitoring the status of a channel and posting events as necessary. When the EVM Channel Manager (evmchmgr ) is started by the EVM daemon, it searches the channel configuration file for channels that define a monitor_function program.
evmchannel.conf(4) Keyword channel cleanup_time events fn_cleanup fn_details fn_explain fn_get fn_monitor mon_period name path e evmchannel.conf(4) Minimum 4 0 5 8 0 6 0 6 0 0 0 Notes If you are concerned with allowing your file to be used on other systems that support EVM in the future, you should use the built-in macro @SYS_VP@ in place of the first two components (sys.unix ) of the name of any system event.
evmchannel.conf(4) evmchannel.conf(4) FILES /etc/evmchannel.conf Location of the EVM channel configuration file. SEE ALSO Commands evmget(1), evmshow(1), evmchmgr(1M), evmd(1M). Files evmdaemon.conf(4), evmlogger.conf(4). Event Management EVM(5). e Event Filter EvmFilter(5).
evmdaemon.conf(4) evmdaemon.conf(4) NAME evmdaemon.conf - EVM daemon configuration file SYNOPSIS authentdir sourcedir authtimeout synctimeout start_sync max_msg_size filterdir directory directory time_seconds time_seconds command message_size filter_dir activity_monitor { detector name period detect_period threshold detect_thold holdoff detect_delay } e service { name service_name command service_command } DESCRIPTION The Event Manager (EVM) daemon configuration file, evmdaemon.
evmdaemon.conf(4) evmdaemon.conf(4) locations. If specified, the daemon uses this value internally to evaluate filter strings that reference pre-created filter files, and also passes it to service programs such as the event retrieval service program, evmget_srv , by exporting the environment variable EVM_FILTERDIR. This makes the path available to the event channels’ get-function scripts. The default value for this keyword is /usr/share/evm/filters. See the evmfilterfile(4) manpage for more information.
evmdaemon.conf(4) evmdaemon.conf(4) The activity monitor detectors recognized, and the action taken when the monitor is activated are the following: Detector event_count Action post an event to alert the system administrator EXAMPLES This is an example of an EVM daemon configuration file that does the following: 1. Specifies that event templates are found in the directory /usr/share/evm/templates. 2. Starts the EVM Logger and the EVM Channel Manager as synchronized clients when the daemon is started. 3.
evmfilterfile(4) evmfilterfile(4) NAME evmfilterfile - Event Manager filter file SYNOPSIS filter { name valuex include exclude title } filter_name filter_value filter_element filter_element filter_title DESCRIPTION A filter file contains one or more filter descriptions, which can be referenced through certain EVM commands by using indirect filter syntax.
evmfilterfile(4) exclude evmfilterfile(4) "[name *.oldlog]" The previous filter lines are equivalent to this more complex single filter line: value "([priority >= 200]) OR [name *.mylog] AND NOT [name *.oldlog]" The first line selects all events with a priority of 200 or greater, the next modifies this by selecting all events from mylog regardless of their priorities, and the last line excludes all oldlog events regardless of their priorities.
evmfilterfile(4) evmfilterfile(4) Event Management EVM(5). EVM Events EvmEvent(5). Event Filter EvmFilter(5).
evmlogger.conf(4) evmlogger.conf(4) NAME evmlogger.
evmlogger.conf(4) evmlogger.conf(4) eventlog Introduces a group of keyword/value pairs, which define an event log. Events that match the log’s log_filter_spec are selected for handling by this log. name eventlog_name The name of the event log. type log_type The type of the log. Specify either formatted or binary . If the log_path specifies a terminal device, such as /dev/console , the type is automatically set to formatted and cannot be forced to binary .
evmlogger.conf(4) evmlogger.conf(4) logger inserts or updates the repeat_count and last_timestamp data items in the last-logged instance of the event. The suppression is indicated by the string [n times] appearing in the message text when the event is displayed, where n is the repeat_count . When an individual event becomes eligible for suppression, the suppression is canceled automatically after four hours or after supp_period, which ever is the greater amount of time.
evmlogger.conf(4) evmlogger.conf(4) NO, or 0 (zero), the forwarder handles events posted through the local daemon. Because EVM currently supports only local connection, this argument should not be set to TRUE. suppress Event suppression as applied to forwarding is similar to event log suppression. The difference is that event suppression for forwarding limits the number of identical events that are forwarded over the suppression period.
evmlogger.conf(4) Keyword alternate command configdir eventlog exclude explicit_target filter forward include logfile maxqueue maxsize name period show_template suppress threshold type e evmlogger.conf(4) Minimum 3 4 7 0 3 4 4 4 3 3 4 3 0 0 4 4 0 0 Notes 1. The logger only allows a single instance of each forwarding command to execute at one time and queues any events that arrive while an instance is already running. The forwarder ignores events that arrive while the queue is full.
evmlogger.conf(4) evmlogger.conf(4) filter "[prio >= 200]" # Suppress logging of duplicate events: suppress { filter "[name *]" period 30 # minutes threshold 3 # No.
evmtemplate(4) evmtemplate(4) NAME evmtemplate - Event Manager template file SYNOPSIS event { event_name name format format_specifier priority priority i18n_catalog i18n_cat i18n_set_id i18n_set i18n_msg_id i18n_msg reference reference_string var { variable_name name type variable_type value variable_value i18n_msg_id variable_value } } e DESCRIPTION A template event is a description of an event that is held centrally by EVM.
evmtemplate(4) Posted Name myco.myprod.env myco.myprod.env.temp.high.70 myco.myotherprod myco.myotherprod evmtemplate(4) Template Name myco.myprod.env myco.myprod.env myco.myprod myco.myotherprod.start Match? Yes Yes No No The syntax of an event template file is identical to the syntax of a file given as input to the evmpost command. The following keywords may be specified in a template file: event This keyword introduces an event group. The body of the group is delimited by braces.
evmtemplate(4) evmtemplate(4) i18n_msg_id i18n_msg Identifies the I18N catalog message to be used in place of the format data item when the event is formatted for display. This item is ignored if no i18n_cat is supplied. If an i18n_set has been specified, the i18n_msg must refer to a message identifier within the given set. If the catalog is missing, or if the i18n_set or i18n_msg values do not refer to a message in the catalog, the event’s format data item is used.
evmtemplate(4) } event { name priority format var } event { name priority format var } evmtemplate(4) myco.myapp.env.temp.high 500 "myapp: Temperature exceeds 80F ($temp)" { name temp type FLOAT value 0.0 } myco.myapp.env.app_terminated 300 "myapp: Production monitoring terminated - code $exit_code" { name exit_code type INT16 value 0 } e FILES /usr/share/evm/templates The root of the directory tree containing system event template files.
exports(4) exports(4) (TO BE OBSOLETED) NAME exports, xtab - directories to export to NFS clients SYNOPSIS /etc/exports /etc/xtab DESCRIPTION The /etc/exports file is obsolete and has been replaced by the new NFS file /etc/dfs/dfstab. Please see dfstab(4) for more details. The /etc/xtab file is also obsolete and has been replaced by the new NFS file /etc/dfs/sharetab. Please see sharetab(4) for more details. e The exports and the xtab files are no longer used to export NFS directories.
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 . /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. The order of entries in /etc/fstab is important only for entries without a pass number field.
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) FILES /etc/fstab /usr/include/fstab.h SEE ALSO crashconf(1M), fsck(1M), mount(1M), swapon(1M), getfsent(3X), getmntent(3X), mnttab(4).
fstypes(4) fstypes(4) NAME fstypes - file that registers distributed file system packages DESCRIPTION fstypes resides in the directory /etc/dfs and lists distributed file system utilities packages installed on the system. For each installed distributed file system type, there is a line that begins with the file system type name (for example, nfs ), followed by white space and descriptive text. The file system indicated in the first line of the file is the default file system.
ftpaccess(4) ftpaccess(4) NAME ftpaccess - ftpd configuration file SYNOPSIS /etc/ftpd/ftpaccess DESCRIPTION The /etc/ftpd/ftpaccess file is used to configure the operation of ftpd (see ftpd(1M)). Access Capabilities autogroup groupname class [ class ... ] If an anonymous user is a member of any of class, the ftp server will perform a setgid() to groupname. This allows access to group-and-owner-read-only files and directories to a particular class of anonymous users.
ftpaccess(4) ftpaccess(4) The group name may be specified by either name or numeric ID. To use a numeric group ID, place a % before the number. Ranges may be given. Use an asterisk (*) to mean all groups. guestuser works like guestgroup , except it uses the user name (or numeric ID). realuser and realgroup have the same syntax, but reverse the effect of guestuser and guestgroup . They allow real user access when the remote user would otherwise be determined a guest.
ftpaccess(4) ftpaccess(4) daemon’s use of this protocol. The information obtained via RFC931 is recorded in the system logs and is not actually used in any authentication. ascii_count [ bytes ] Specify the number of bytes after which the data connection idle time is reset, in case of an ASCII mode file transfer (see timeout data above for more information). The number specified must be a positive power of 2. By default, the number is set to 4096 bytes.
ftpaccess(4) ftpaccess(4) The noretrieve restrictions may be placed upon members of particular classes. If any class= is specified, then this option is set only for the users of that particular class. allow-retrieve [ absolute |relative ] [ class= classname ] ... [-] filename [ filename ] ... Allows retrieval of files which would otherwise be denied by noretrieve. loginfails number After number login failures, log a message and terminate the FTP connection. Default value is 5.
ftpaccess(4) ftpaccess(4) message path [ when [ class... ]] Define a file with path such that ftpd will display the contents of the file to the user at login time or upon using the change working directory command. The when parameter may be LOGIN or CWD= dir. If when is CWD= dir, dir specifies the new default directory which will trigger the notification. The optional class specification allows the message to be displayed only to members of a particular class. More than one class may be specified.
ftpaccess(4) ftpaccess(4) The optional class specification allows the message to be displayed only to members of a particular class. More than one class may be specified. Logging Capabilities log commands typelist Enables logging of individual commands by users. typelist is a comma-separated list of any of the keywords anonymous , guest and real .
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 f The directory will be searched for in the following order: .
ftpaccess(4) ftpaccess(4) root path Normally used in a virtual host ftpaccess file, the root directive is used to specify the path to the root of the ftp directory for this server. virtual address { root |banner |logfile } path Enables the virtual ftp server capabilities. The address is the IP address of the virtual server. The second argument specifies that the path is one of the following: root banner logfile The root of the filesystem for this virtual server.
ftpaccess(4) ftpaccess(4) defaultserver private Normally, anonymous users are allowed on the default (non-virtual) FTP server. This statement disallows anonymous access. The virtual and defaultserver allow , deny , and private clauses provide a means to control which users are allowed access on which FTP servers. passive address externalip cidr Allows control of the address reported in response to a PASV command.
ftpaccess(4) ftpaccess(4) incmail emailaddress virtual address incmail emailaddress defaultserver incmail emailaddress Specify email addresses to be notified of anonymous uploads. Multiple addresses can be specified; each will receive a notification. If none are specified, no notifications are sent. If addresses are specified for a virtual host, only those addresses will receive notification up anonymous uploads on that host. Otherwise, notifications will be sent to the global addresses.
ftpaccess(4) ftpaccess(4) specifies that all upload filenames for anonymous users must be made of only the characters A-Z , az, 0-9 , period (.), dash (-), and underscore (_). The filenames may not begin with a period (.) or a dash (-) as specified by ˆ\. and ˆ- respectively. If the filename is invalid, /etc/pathmsg will be displayed to the user. upload [ absolute |relative ] [ class= classname ]...
ftpaccess(4) ftpaccess(4) guest-root root-dir [ uid-range ... ] root-dir specifies the chroot() path for guest users. If guest-root is not matched, the old method of parsing the user’s home directory is used. If no uid-range is specified, the root directory is for guest users who do not match any other guest-root specification. Multiple uid ranges may be given on the line.
ftpaccess(4) ftpaccess(4) Wherever possible, in situations such as this example, try not to rely solely upon the ftp restrictions. As with all other ftp access rules, try to use directory and file permissions to backstop the operation of the ftpaccess configuration. site-exec-max-lines number [ class ... ] The SITE EXEC feature traditionally limits the number of lines of output which may be sent to the remote client. This clause allows you to set this limit. If omitted, the limit is 20 lines.
ftpconversions(4) ftpconversions(4) NAME ftpconversions - ftpd conversions database SYNOPSIS /etc/ftpd/ftpconversions DESCRIPTION The conversions known by ftpd and their attributes are stored in an ASCII file that is structured as below. Each line in the file provides a description for a single conversion. Fields are separated by colons (:).
ftpgroups(4) ftpgroups(4) NAME ftpgroups - group password file for use with the SITE GROUP and SITE GPASS commands. SYNOPSIS /etc/ftpd/ftpgroups DESCRIPTION The ftpgroups file is the group password file for use with the SITE GROUP and SITE GPASS commands. To enable the use of this file, the entry private /etc/ftpd/ftpaccess. yes must be made in the configuration file This file contains an alphanumeric string, encrypted password, and the actual group name from the /etc/group file.
ftphosts(4) ftphosts(4) NAME ftphosts - ftpd individual user host access file SYNOPSIS /etc/ftpd/ftphosts DESCRIPTION The /etc/ftpd/ftphosts file is used to allow or deny access to certain accounts from various hosts. Access Capabilities allow username addrglob [ addrglob... ] Only allow host(s) matching addrglob to log in as username. addrglob is a globbed domain name or a globbed numeric address. deny username addrglob [ addrglob ... ] f Always deny host(s) matching addrglob to log in as username.
ftpservers(4) ftpservers(4) NAME ftpservers - ftpd virtual hosting configuration specification file SYNPOSIS /etc/ftpd/ftpservers DESCRIPTION The /etc/ftpd/ftpservers file is used to tell which set of virtual domain configuration files that the ftpd server should use. With VIRTUAL support, wu-ftpd has the ability to use separate configuration files for each virtual domain. For a virtual host, configuration files can be placed into a separate virtual domain directory.
ftpusers(4) ftpusers(4) NAME ftpusers - security file for ftpd 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) 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) nonbroadcast multiaccess or nbma This type of interface is multiaccess, 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) 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. Point-to-point interfaces also support this additional parameter: nomulticast By default, OSPF packets to neighbors on point-to-point interfaces are sent via the IP multicast mechanism.
gated.conf(4) gated.conf(4) 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. Computers communicating via EGP are called EGP neighbors, and the exchange of HELLO and I-H-U messages is referred to as acquiring a neighbor.
gated.conf(4) gated.conf(4) 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) 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) Nonrouting 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 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. /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) ftp Deny all access to the shell service; i.e., remsh : shell deny 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.
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 ).
ioconfig(4) ioconfig(4) NAME ioconfig - ioconfig entry format SYNOPSIS #include DESCRIPTION The ioconfig file is used to retain information on a system’s I/O 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 insf(1M), ioinit(1M), ioscan(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 brackets, [ ]. Within each section, there are relations where tags can be assigned to have specific values.
krb5.conf(4) krb5.conf(4) by the client, in the same format. permitted_enctypes Identifies the permitted list of session key encryption types. clockskew 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. kpasswd_timeout Sets the timeout value for the amount of time (in seconds) to wait for a response from an admin server.
krb5.conf(4) krb5.conf(4) appdefaults Section Each tag in the [appdefaults] section names a Kerberos V5 application or an option that is used by some Kerberos V5 application(s). The value of the tag is a subsection with relations that define the default behaviors for that application.
krb5.conf(4) krb5.conf(4) • If none of the servers listed above the secondary server respond, then admin_server will update the password on the secondary. default_domain 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) The severity argument specifies the default severity of system log messages. This may be any of the following severities mentioned below supported by the syslog() call (see syslog(3C)). The supported arguments are: LOG_ALERT LOG_CRIT LOG_DEBUG LOG_EMERG LOG_INFO LOG_NOTICE LOG_ERR LOG_WARNING For example, to specify LOG_CRIT severity, you would use CRIT for severity . The LOG_ prefix is deleted.
krb5.conf(4) krb5.conf(4) TEST.ANL.GOV = { ANL.GOV = } PNL.GOV = { ANL.GOV = } NERSC.GOV = { ANL.GOV = } ES.NET = { ANL.GOV = } . ES.NET ES.NET . 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.
krb5.conf(4) krb5.conf(4) SEE ALSO syslog(3C), Kerberos(5), ldapux(5).
ldapclientd.conf(4) ldapclientd.conf(4) NAME ldapclientd.conf - configuration file for the LDAP client daemon process SYNOPSIS /etc/opt/ldapux/ldapclientd.conf DESCRIPTION ldapclientd.conf is the configuration file for /opt/ldapux/bin/ldapclientd, an LDAP client daemon process that enables LDAP-UX clients to work with Directory Servers.
ldapclientd.conf(4) ldapclientd.conf(4) Default value is 100. connection_ttl=1-2147483647 Seconds before an inactive connection to the directory server is brought down and cleaned up. Default value is 300. num_threads= 1-100 Number of client request handling threads in ldapclientd . Default value is 10. socket_cleanup_time=10-2147483647 Interval (seconds) before next attempt to clean up socket files created by LDAP-UX client applications that were terminated abnormally. Default value is 300.
ldapclientd.conf(4) ldapclientd.conf(4) negcache_ttl= 1-2147483647 Seconds before a cache entry expires from the negative cache. Like, poscache_ttl , there is no [general] default value for this setting. Each cache section has its own default. [passwd] Cache settings for the passwd cache (which caches name, uid, and shadow information). The valid setting under this section are: enable=yes |no ldapclientd only caches entries for this section when it is enabled.
ldapclientd.conf(4) ldapclientd.conf(4) Typically, once added into a directory, the user’s DN rarely changes. Default value is 86400. negcache_ttl= 1-2147483647 Seconds before a cache entry expires from the negative cache. Default value is 86400. [domain_pwd] This cache maps user names and UID’s to the domain holding its entry. enable=yes |no ldapclientd only caches entries for this section when it is enabled. By default, caching is enabled.
ldapclientd.conf(4) ldapclientd.conf(4) poscache_ttl= 0-2147483647 Seconds before a cache entry expires from the positive cache. Typically, once added into a directory, the map’s DN rarely changes. Default value is 1800. negcache_ttl= 1-2147483647 Seconds before a cache entry expires from the negative cache. Default value is 7200. [printers] User configurable parameters for the printer configurator. start= yes |no Define the status of the printer configurator when ldapclientd starts.
ldapclientd.conf(4) ldapclientd.conf(4) enable=yes [domain_pwd] enable=yes [domain_grp] enable=yes [automount] enable=yes [automountmap] enable=yes [printers] start=yes max_printers=50 search_interval=86400 DIAGNOSTICS problem reading configuration file When ldapclientd starts, it reads the configuration file and points out errors during parsing. This error message is accompanied by the line showing exactly where ldapclientd could not recognize the syntax or found that the setting is out of range.
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) SEE ALSO lifcp(1), lifinit(1), lifls(1), lifrename(1), lifrm(1).
localedef(4) localedef(4) NAME localedef - format and semantics of locale definition file DESCRIPTION This is a description of the syntax and meaning of the locale definition that is provided as input to the localedef command to create a locale (see localedef(1M)). The following is a list of category tags, keywords and subsequent expressions which are recognized by localedef .
localedef(4) localedef(4) 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) from the value. If the currency symbol and sign string are adjacent, a space separates them; otherwise, a space separates the sign string from the value. 2 n_cs_precedes The operand is an integer which if set to 1 indicates the currency_symbol precedes a negative monetary quantity, and if set to 0 the symbol succeeds the negative value.
localedef(4) localedef(4) LC_NUMERIC and END LC_NUMERIC : decimal_point The operand is a string containing the symbol used as the decimal delimiter (radix character) in numeric, non-monetary formatted quantities. This keyword cannot be omitted and cannot be set to the empty string. thousands_sep The operand is a string containing the symbol used as a separator for groups of digits to the left of the decimal delimiter. grouping The operand is a semicolon-separated list of integers.
localedef(4) localedef(4) negative numbers. For example, an era beginning March 5th in the year 100 B.C. would be represented as 3-100/3/5 . Years in the range [SHRT_MIN+1,SHRT_MAX-1] are supported. end_date The ending date of the era in the same form as the start_date above or one of the two special values -* or +* . A value of -* indicates the ending date of the era extends to the beginning of time while +* indicates it extends to the end of time.
localedef(4) localedef(4) ellipsis. A range represents a set of consecutive character codes. If the list is longer than a single line, the escape character must be used at the end of each line as a continuation character. It is an error to use any symbolic name that is not defined in an accompanying charmap file (see charmap(4)). string lists string list operands consist of strings separated by semicolons. If longer than one line, the escape character must be used for continuation.
localedef(4) shift localedef(4) Shift operands follow keywords toupper and tolower , and must consist of two character-code constants enclosed by left and right parentheses and separated by a comma. Each such character pair is separated from the next by a semicolon. For tolower , the first constant represents an uppercase character and the second the corresponding lowercase character. For toupper , the first constant represents an lowercase character and the second the corresponding uppercase character.
localedef(4) localedef(4) is: ’-’ IGNORE;’-’ Symbols defined by the collating-symbol keyword can be used to indicate that a given character collates higher or lower than some position in the sequence.
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), intro(7), lvm(7).
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.
mech(4) mech(4) NAME mech, qop - security mechanism and quality of protection (QOP) files SYNOPSIS /etc/gss/mech /etc/gss/qop DESCRIPTION The /etc/gss/mech and /etc/gss/qop files contain tables showing installed security mechanisms and the Quality of Protection (QOP) associated with them, respectively. These files are accessed by GSSAPI calls; see gssapi(5). As security mechanisms are installed on the system, entries are added to these two files.
mnttab(4) mnttab(4) NAME mnttab - mounted file system table SYNOPSIS #include DESCRIPTION mnttab resides in directory /etc and contains a table of devices mounted by the mount command (see mount(1M)). The file contains a line of information for each mounted filesystem which is structurally identical to the contents of /etc/fstab described by fstab(4).
model(4) model(4) (TO BE OBSOLETED) NAME model - HP-UX machine identification SYNOPSIS #include DESCRIPTION There are certain inevitable distinctions between HP-UX implementations due to hardware differences. Where such distinctions exist, conditional compilation or other definitions can be used to isolate the differences. Flags and typedefs to resolve these distinctions are collected in the header file which contains constants identifying various HP-UX implementations.
named.conf(4) named.conf(4) (BIND 9.3) NAME named.conf - configuration file for Internet domain name server SYNOPSIS /etc/named.conf DESCRIPTION named.conf is the configuration file for the named name server daemon. The default path name is /etc/named.conf. BIND 9 configuration is broadly similar to BIND 8.x. However, there are a few new areas of configuration, such as views. BIND 8.x configuration files should work with few alterations in BIND 9.
named.conf(4) named.conf(4) (BIND 9.3) path_name A quoted string that is used as a path name, such as "zones/master/my.test.domain". size_spec One of the following: number A decimal number, optionally be followed by a scaling factor: K or k for kilobytes, M or m for megabytes, and G or g for gigabytes, which scale by 1024, 1024*1024, and 1024*1024*1024 respectively. The value must be representable as a 64-bit unsigned integer (0 to 18446744073709551615, inclusive).
named.conf(4) named.conf(4) (BIND 9.3) Comment Syntax Comments in the BIND 9.3 configuration file can be written in the following styles: C: C++: UNIX: /* comment */ // to end of line # to end of line Note: Unlike a zone file, you cannot use a semicolon (;) character to start a comment in the BIND 9.3 configuration file. The semicolon indicates the end of a configuration statement. CONFIGURATION FILE GRAMMAR A BIND 9.3 configuration file consists of statements and comments.
named.conf(4) named.conf(4) (BIND 9.3) The controls Statement controls Statement Grammar controls { ( inet ( ip_addr | * ) [ port ip_port ] allow { address_match_list } keys { key_list }; )... }; controls Statement Definition and Usage The controls statement declares control channels to be used by system administrators to control the operation of the local name server. These control channels are used by the rndc utility to send commands to and retrieve non-DNS results from a name server.
named.conf(4) named.conf(4) (BIND 9.3) key Statement Definition and Usage The key statement defines a shared secret key for use with TSIG. The key statement can occur at the top level of the configuration file or inside a view statement. Keys defined in top-level key statements can be used in all views. Keys intended for use in a controls statement must be defined at the top level. key_id A domain name uniquely identifying the key. Also known as the key name.
named.conf(4) named.conf(4) (BIND 9.3) The file destination clause directs the channel to a disk file. It can include limitations on both the file size and the number of versions of the file that are saved each time the file is opened. If you use the versions log file option, then named will retain that many backup versions of the file by renaming them when opening. For example, if you choose to keep three old versions of the file lamers.log , then, just before it is opened: lamers.log.
named.conf(4) named.conf(4) (BIND 9.3) If print-time is on, then the date and time will be logged. print-time may be specified for a syslog channel, but that is usually pointless, since syslog also prints the date and time. If print-category is on , then the category of the message is logged as well. If print-severity is on , then the severity level of the message will be logged. The print-* options may be used in any combination, and will always be printed in the order time, category, severity.
named.conf(4) named.conf(4) (BIND 9.
named.conf(4) named.conf(4) (BIND 9.3) The lwres Statement lwres Statement Grammar lwres { [ listen-on { ( ip_addr [ port ip_port ] ; )... }; ] [ ndots number ; ] [ search { domain_name ; [ domain_name ; ]... }; ] [ view view_name ; ] }; lwres Statement Definition and Usage The lwres statement configures the name server to also act as a lightweight resolver server. There may be be multiple lwres statements configuring lightweight resolver servers with different properties.
named.conf(4) named.conf(4) (BIND 9.
named.conf(4) named.conf(4) (BIND 9.3) // Query Address Options [ query-source [ address ( ip_addr | * ) ] [ port ( ip_port | * ) ] ; ] [ query-source-v6 [ address ( ip_addr | * ) ] [ port ( ip_port | * ) ] ; ] // RRset Ordering Option [ rrset-order { order_spec ; [ order_spec ; ]...
named.conf(4) named.conf(4) (BIND 9.3) specified should be an absolute path. disable-algorithms Disable the specified DNSSEC algorithms at and below the specified name. Multiple disable-algorithms statements are allowed. Only the most specific is applied. dnssec-lookaside When set, dnssec-lookaside provides the validator with an alternate method to validate DNSKEY records at the top of a zone.
named.conf(4) named.conf(4) (BIND 9.3) The Statistics File section. tkey-dhkey The Diffie-Hellman key used by the server to generate shared keys with clients using the Diffie-Hellman mode of TKEY. The server must be able to load the public and private keys from files in the working directory. In most cases, the key_name should be the server’s host name. The key_tag is an integer that is part of the key. tkey-domain The domain appended to the names of all shared keys generated with TKEY.
named.conf(4) named.conf(4) (BIND 9.3) (the owner name ends in IN-ADDR.ARPA , IP6.ARPA , IP6.INT ). dialup If yes , then the server treats all zones as if they are doing zone transfers across a dial-ondemand dialup link, which can be brought up by traffic originating from this server. This has different effects according to zone type and concentrates the zone maintenance so that it all happens in a short interval, once every heartbeat-interval and hopefully during the one call.
named.conf(4) named.conf(4) (BIND 9.3) Caching may still occur as an effect of the server’s internal operation, such as NOTIFY address lookups. request-ixfr Determines whether the local server, acting as a slave, will request incremental zone transfers from the given remote server, a master. If not set in a server statement, the value of the request-ixfr option in the view or global options statement is used as a default.
named.conf(4) named.conf(4) (BIND 9.3) hide the built-in CHAOS view by defining an explicit view of class CHAOS that matches all clients. hostname The host name the server should report via a query of the name hostname.bind with type TXT , class CHAOS . This defaults to the host name of the machine hosting the name server as found by gethostname() (see gethostname(2)). The primary purpose of such queries is to identify which of a group of anycast servers is actually answering your queries.
named.conf(4) named.conf(4) (BIND 9.3) allowed for the address_match_list argument of the listen-on-v6 statement are: {any;} and {none;} . Multiple listen-on-v6 options can be used to listen on multiple ports: listen-on-v6 port 53 { any; }; listen-on-v6 port 1234 { any; }; To make the server not to listen on any IPv6 address, use listen-on-v6 { none; }; If no listen-on-v6 statement is specified, the server will not listen on any IPv6 address.
named.conf(4) named.conf(4) (BIND 9.3) Query Address Options If the server is unable to answer a question, it will query other name servers. query-source Specifies the address and port used for such queries. query-source-v6 Specifies the address and port used for queries sent over IPv6. If address is * or is omitted, a wildcard IP address (INADDR_ANY ) is used. If port is * or is omitted, a random unprivileged port will be used.
named.conf(4) named.conf(4) (BIND 9.3) tcp-clients The maximum number of simultaneous client TCP connections that the server will accept. The default is 100. tcp-listen-queue The listen queue depth. The default and minimum is 3. If the kernel supports the accept filter "dataready", this also controls how many TCP connections that will be queued in kernel space waiting for some data before being passed to accept. Values less than 3 are silently raised.
named.conf(4) named.conf(4) (BIND 9.3) sortlist { { localhost; localnets; }; { localnets; }; }; Tuning Options edns-udp-size Sets the advertised Extended DNS (EDNS) UDP buffer size in bytes. Valid values are 512 to 4096 (values outside this range will be silently adjusted). The default value is 4096. The usual reason for setting edns-udp-size to a nondefault value is to get UDP answers to pass through broken firewalls that block fragmented packets and/or block UDP packets that are greater than 512 bytes.
named.conf(4) named.conf(4) (BIND 9.3) max-transfer-idle-out Outbound zone transfers making no progress in this many minutes will be terminated. The default is 60 minutes (1 hour). The maximum value is 28 days (40320 minutes). max-transfer-time-in Inbound zone transfers running longer than this many minutes will be terminated. The default is 120 minutes (2 hours). The maximum value is 28 days (40320 minutes).
named.conf(4) named.conf(4) (BIND 9.3) phrase of the server statement. use-alt-transfer-source Use the alternate transfer sources or not. If views are specified, this defaults to no ; otherwise, it defaults to yes (for BIND 8 compatibility). The server Statement server Statement Grammar server [ [ [ [ [ [ [ [ [ }; ip_addr { bogus yes_or_no ; ] edns yes_or_no ; ] keys { string ; [ string ; ]...
named.conf(4) named.conf(4) (BIND 9.3) specified, the transfer-format specified by the options statement is used. transfer-source, transfer-source-v6 Specify the IPv4 and IPv6 source address to be used for zone transfer with the remote server, respectively. For an IPv4 remote server, only transfer-source can be specified. Similarly, for an IPv6 remote server, only transfer-source-v6 can be specified. transfers Limits the number of concurrent inbound zone transfers from the specified server.
named.conf(4) named.conf(4) (BIND 9.3) zone options can have default values specified in the view statement; these view-specific defaults take precedence over those in the options statement. See The options Statement section. zone_statement Zones defined within a view statement will only be accessible to clients that match the view. By defining a zone of the same name in multiple views, different zone data can be given to different clients; for example, internal and external clients in a split DNS setup.
named.conf(4) named.conf(4) (BIND 9.3) ( masters_name | ip_addr [ port ip_port ] [ key key ] ) ; )...
named.conf(4) named.conf(4) (BIND 9.3) stub children of that zone. This meant that, in some cases, users could get away with configuring child stubs only in the master server for the parent zone. BIND 9 never mixes together zone data from different zones in this way. Therefore, if a BIND 9 master serving a parent zone has child stub zones configured, all the slave servers for the parent zone also need to have the same child stub zones configured.
named.conf(4) named.conf(4) (BIND 9.3) alt-transfer-source-v6 See the description in The options Statement section. check-names Restrict the character set and syntax of certain domain names in master files and/or DNS responses received from the network. The default varies according to zone type. For master zones, the default is fail . For slave zones, the default is warn . database Specify the type of database to be used for storing the zone data.
named.conf(4) named.conf(4) (BIND 9.3) max-transfer-time-out See the description in The options Statement section. min-refresh-time See the description in The options Statement section. min-retry-time See the description in The options Statement section. multi-master This should be set when you have multiple masters for a zone and the addresses refer to different machines. If yes , named will not log when the serial number on the master is less than what named currently has. The default is no .
named.conf(4) named.conf(4) (BIND 9.3) the rule will apply to multiple identities. The identity field must contain a fully qualified domain name. The nametype field has four possible values: name Exact-match semantics. This rule matches when the name being updated is identical to the contents of the name field. subdomain This rule matches when the name being updated is a subdomain of, or identical to, the contents of the name field.
named.conf(4) named.conf(4) (BIND 9.3) An origin in a zone file is an absolute domain name that is appended to a relative domain name to complete it. For example, if example.com. is the origin and myhost is a relative domain name, they would combine to form the absolute domain name, myhost.example.com.. A comment starts with a semicolon (;) and continues to the end of the line.
named.conf(4) named.conf(4) (BIND 9.3) Syntax $TTL default-ttl default-ttl The default TTL value for subsequent RRs. See the Time to Live (TTL) and Time Specification sections for more detail. The $GENERATE Directive The $GENERATE directive creates a series of resource records that differ from each other only by an iterator value. $GENERATE is a BIND extension and not part of the standard DNS zone file format.
named.conf(4) named.conf(4) (BIND 9.3) A domain name identifies a node. Each node has a set of resource information, which may be empty. The set of resource information associated with a particular name is composed of separate RRs. The order of RRs in a set is not significant and need not be preserved by name servers, resolvers, or other parts of the DNS. However, the sorting of multiple RRs is permitted for optimization purposes, for example, to specify that a particular nearby server be tried first.
named.conf(4) named.conf(4) (BIND 9.3) 2874. AAAA CERT CNAME DNAME Defines an IPv6 address. Described in RFC 1886. GPOS HINFO KEY KX MX Specifies the global position. Described in RFC 1712. NAPTR NSAP NS NXT Name authority pointer. Described in RFC 2915. PTR Domain name pointer. A pointer to another part of the domain name space. Often user to associate an IP address with a domain name. Described in RFC 1035. PX Provides mappings between RFC 822 and X.400 addresses. Described in RFC 2163.
named.conf(4) named.conf(4) (BIND 9.3) An MX record must have an associated A record; a CNAME is not sufficient. For a given domain, if there is both a CNAME record and an MX record, the MX record is in error and will be ignored. Instead, the mail will be delivered to the server specified in the MX record pointed to by the CNAME . Example example.com. mail.example.com. mail2.example.com. IN IN IN IN IN MX MX MX A A 10 mail.example.com. 10 mail2.example.com. 20 mail.backup.org. 10.0.0.1 10.0.0.
named.conf(4) named.conf(4) (BIND 9.3) zone. The TTL is assigned by the administrator for the zone where the data originates. While short TTLs can be used to minimize caching, and a zero TTL prohibits caching, the realities of Internet performance suggest that these times should be on the order of days for the typical host.
named.conf(4) named.conf(4) (BIND 9.3) This example shows six RRs, with two RRs at each of three domain names. AUTHOR named.conf and the $GENERATE directive were developed by the Internet Systems Consortium (ISC). Zone files were developed by the Internet Engineering Task Force (IETF). FILES /dev/random /etc/named.conf Default named configuration file. /etc/resolv.conf /etc/rndc.key /usr/bin/named-bootconf.sh Shell script to convert BIND 4.9.7 configuration files to the BIND 9.3 format. /var/run/named.
netconfig(4) netconfig(4) NAME netconfig - network configuration database SYNOPSIS /etc/netconfig DESCRIPTION The network configuration database, /etc/netconfig, is a system file used to store information about networks that are connected to the system. The netconfig database and the routines that access it (see getnetconfig(3N)) are part of the Network Selection component. The Network Selection component also includes getnetpath() routines to provide application-specific network search paths.
netconfig(4) netconfig(4) network_device The network_device is the full pathname of the device used to connect to the transport provider. Typically, this device will be in the /dev directory. The network_device must be specified. translation_libraries The name-to-address translation libraries support a ‘‘directory service’’ (a name-to-address mapping service) for the network. A ‘‘-’’ in this field indicates the absence of any translation_libraries.
netconfig(4) netconfig(4) # gethostbyname, gethostbyaddr, getservbyname, and getservbyport. # There are no nametoaddr_libs for the inet family, and currently # nametoaddr_libs are not supported. # udp tpi_clts v inet udp /dev/udp tcp tpi_cots_ord v inet tcp /dev/tcp AUTHOR netconfig was developed by Sun Microsystems, Inc. FILES /etc/netconfig SEE ALSO getnetconfig(3N), getnetpath(3N), nsswitch.conf(4).
netgroup(4) netgroup(4) NAME netgroup - list of network groups DESCRIPTION File /etc/netgroup defines network-wide groups, and is used for permission checking when executing remote mounts, remote logins, and remote shells. For remote mounts, the information in netgroup classifies machines; for remote logins and remote shells, it classifies users. Each line of the netgroup file defines a group. The items on a line may be separated by a combination of one or more spaces or tabs.
netrc(4) netrc(4) NAME netrc: .netrc - login information for ftp, rexec, 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) 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 and logging configuration file SYNOPSIS /etc/nettlgen.conf DESCRIPTION /etc/nettlgen.conf, the configuration file for Common Network Tracing and Logging commands commands, contains configuration information used by the nettl , and netfmt commands (see nettl(1M), and netfmt(1M)).
nettlgen.conf(4) nettlgen.conf(4) default size is 8192 bytes (specified by 8), which is split into thirty-two 256-byte blocks. The first block is reserved by the system, leaving 31 blocks for log messages. Each log message starts on a new block, taking 64 bytes of overhead. In addition, each block takes 8 bytes of overhead. The largest message that can be stored using the default size is 7624 bytes ((31 * 256) - (31 * 8) - 64).
nettlgen.conf(4) nettlgen.conf(4) 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. The recommended setting for the default logging level is set by the products’ configuration scripts.
nettlgen.conf(4) nettlgen.conf(4) SS:127:FORMATTER:12:u:libfmtutil.sl:netfmt: \ subsys_GENERIC_format:subsys_127_get_options:FORMATTER FILES /etc/nettlgen.conf SEE ALSO netfmt(1M), nettl(1M), nettlconf(1M).
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.
nfs(4) nfs(4) NAME nfs - file containing parameter values for NFS-related daemons SYNOPSIS /etc/default/nfs DESCRIPTION The nfs file resides in directory /etc/default and provides startup parameters for the nfsd and lockd daemons. The nfs file format is ASCII; comment lines begin with the crosshatch (#) character. Parameters consist of a keyword followed by an equal sign followed by the parameter value.
nfs(4) nfs(4) NFSD_DEVICE= devname Start NFS daemon for the transport specified by the given device only. Equivalent to the -t option in nfsd . Mutually exclusive of NFSD_PROTOCOL. Either NFSD_DEVICE or NFSD_PROTOCOL must be commented out. NFSD_SERVERS=num Maximum number of concurrent NFS requests. Equivalent to last numeric argument on the nfsd command line. The default is 16. LOCKD_LISTEN_BACKLOG=num Set connection queue length for lockd over a connection-oriented transport.
nfs(4) nfs(4) AUTHOR nfs was developed by Sun Microsystems, Inc. SEE ALSO lockd(1M), mount_nfs(1M), nfsd(1M), nfsmapid(1M).
nfslog.conf(4) nfslog.conf(4) NAME nfslog.conf - NFS server logging configuration file SYNOPSIS /etc/nfs/nfslog.conf DESCRIPTION The nfslog.conf file specifies the location of the NFS server logs, as well as the location of the private work files used by the NFS server and nfslogd(1M) daemon during logging. Each entry in the file consists of a mandatory tag identifier and one or more parameter identifiers. The parameter identifier specifies the value or location of the specific parameter.
nfslog.conf(4) nfslog.conf(4) EXAMPLES Example 1: Using the global Tag The global tag may be modified so that all exported file systems that enabled logging use a common set of parameters that conform to the specific needs of the user. These values are used until a specific tag identifier overrides them.
nfssec.conf(4) nfssec.conf(4) NAME nfssec.conf - list NFS security modes SYNOPSIS /etc/nfssec.conf DESCRIPTION The nfssec.conf file lists the NFS security modes supported on a system. These modes are defined in nfssec(5). The nfssec.conf file should not be edited by a user. SEE ALSO nfssec(5).
nlist(4) nlist(4) NAME nlist, nlist64 - structure formats SYNOPSIS Remarks For Integrity systems, see nlist_ia(4). For PA-RISC systems, see nlist_pa(4). Use the uname command to determine your system type. uname -m returns ia64 on Integrity systems. All other values represent PA-RISC systems. SEE ALSO nlist_ia(4), nlist_pa(4), uname(1).
nlist_ia(4) nlist_ia(4) Integrity Systems Only NAME nlist_ia: nlist, nlist64 - structure formats for Integrity systems SYNOPSIS #include Remarks The exact content of the structure defined below can be best found by examining /usr/include/nlist.h. It varies somewhat between various HP-UX implementations. This manpage describes on Integrity systems. For on PA-RISC systems, see nlist_pa(4).
nlist_pa(4) nlist_pa(4) PA-RISC Systems Only NAME nlist_pa: nlist, nlist64 - structure formats for PA-RISC systems 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. This manpage describes on PA-RISC systems. For on Integrity systems, see nlist_ia(4).
nlspath(4) nlspath(4) (TO BE OBSOLETED) NAME nlspath - NLSPATH configuration file DESCRIPTION The file /etc/default/nlspath allows the superuser to restrict the paths set by others through an environment variable NLSPATH to locate message catalogs for setuid or setgid root programs. This file contains only one entry with the following format: NLSPATH= pseudo-pathname :pseudo-pathname :... pseudo-pathnames in this file should be absolute pathnames and 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, LDAP, or DNS.
nsswitch.conf(4) nsswitch.conf(4) action and status names are case-insensitive. The default criteria are to continue on anything except SUCCESS; in other words, [SUCCESS=return NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue]. 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.conf(4) resolver (4) for more details. hosts: nis dns [NOTFOUND=return] files ipnodes: nis dns [NOTFOUND=return] files The file /etc/nsswitch.ldap contains an example configuration that can be copied to /etc/nsswitch.conf to set an LDAP policy. If the +/- netgroup syntax (used for access control as defined by nis ) is desired, the administrator needs to configure libpam_authz.1 in the /etc/pam.conf file.
nsswitch.conf(4) nsswitch.conf(4) Obsolescence The ipnodes directive may not be supported in future HP-UX releases. In order to minimize the impact to applications, it is recommended that you have the same configuration for the hosts and the ipnodes directives. AUTHOR nsswitch.conf was developed by Sun Microsystems, Inc. FILES A source named SSS is implemented by a shared object named nss_SSS.1 that resides in /usr/lib . /etc/nsswitch.conf /usr/lib/nss_compat.1 /usr/lib/nss_dns.1 /usr/lib/nss_files.
packingrules(4) packingrules(4) NAME packingrules - packing rules file for cachefs DESCRIPTION packingrules is a packing rules file for cachefspack . packingrules contains a list of directories and files that are to be packed. It also contains a list of directories and files that are to be specifically excluded from packing. See cachefspack(1M). Many users choose to manually create the packing rules file and edit it by hand.
packingrules(4) packingrules(4) LIST m/pending # # Pack two important project directories but skip # all postscript output. # BASE /net/bigserver/export/projects $HOME/projects LIST poindexter epiphany IGNORE *.ps # # Pack the foonly package. # BASE /net/bigserver/opt/foonly /opt/foonly LIST !cat .packinglist # # Also pack the latest executables for the standard # build environment. # BASE /net/bigserver/export/buildenv $HOME/buildenv LIST !find .
pam.conf(4) pam.conf(4) NAME pam.conf - configuration file for pluggable authentication modules SYNOPSIS /etc/pam.conf DESCRIPTION /etc/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) /usr/lib/security/ and /usr/lib/security/pa20_64 Example: /usr/lib/security/libpam_unix.so.1 -> ./libpam_unix.1 If a userdefined module is specified in /etc/pam.conf or /etc/pam_user.conf, the above convention must be followed to create symbolic links pointing to PA-RISC modules. To help reduce the impact of any future /etc/pam.conf file format changes, the only supported way of parsing /etc/pam.conf is through the PAM library interfaces.
pam.conf(4) pam.conf(4) In the case of dtlogin , the sufficient keyword for control_flag specifies that if the UNIX authentication check succeeds, then PAM should return success to dtlogin . The inhouse authentication module (the next module in the stack) will only be invoked if the UNIX authentication check fails. Configuration Per User /etc/pam.conf contains information to configure all the users on a system. But sometimes it is necessary to configure user by user.
pam.conf(4) pam.conf(4) login account required libpam_hpsec.so.1 login account required libpam_unix.so.1 login account optional libpam_inhouse.so.1 dtlogin account required libpam_hpsec.so.1 dtlogin account required libpam_unix.so.1 dtlogin account optional libpam_inhouse.so.1 # # Other services use hpsec and UNIX account management other account required libpam_hpsec.so.1 other account required libpam_unix.so.1 # # Session management for login service is stacked.
pam.conf(4) pam.conf(4) login session required libpam_hpsec.so.1 login session required libpam_unix.so.1 login session optional libpam_inhouse.so.1 dtlogin session required libpam_hpsec.so.1 dtlogin session required libpam_unix.so.1 dtlogin session optional libpam_inhouse.so.1 # # Other services use hpsec and UNIX session management other session required libpam_hpsec.so.1 other session required libpam_unix.so.1 # # Password management passwd password required libpam_hpsec.so.
pam_user.conf(4) pam_user.conf(4) NAME pam_user.conf - user 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) john david susan password password password pam_user.conf(4) /usr/lib/security/$ISA/libpam_unix.so.1 /usr/lib/security/$ISA/libpam_unix.so.1 /usr/lib/security/$ISA/libpam_unix.so.1 use_psd 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) /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. The current use of this field is derived from its use within the Berkeley Software Distribution. Future standards may define this field for other purposes.
passwd(4) /etc/shadow passwd(4) Shadow password file. SEE ALSO chfn(1), chsh(1), finger(1), login(1), passwd(1), pwck(1M), 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.
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) SECURITY CONCERNS The file /etc/ppp/Auth should be mode 600 or 400, and owned by root. AUTHOR ppp.Auth was developed by the Progressive Systems. SEE ALSO pppd(1), ppp.Devices(4), ppp.Dialers(4), ppp.Filter(4), ppp.Keys(4), ppp.Systems(4), services(4). RFC 792, RFC 1332, RFC 1334, RFC 1548.
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) EXAMPLES # # Devices # #Dialer device T2500-PEP T1600 cub Direct rsd0a/0 Oddball rsd0a/1 ppp.Devices(4) - PPP devices file speed cua 38400 1536000 64000 Optional parameters 19200-PEP rtscts rtscts internal-clocking 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) number. For IPv6 networks specify a prefix or a IPv6 address with prefix length separated by a slash (/). The sense of a stanza may be negated by prefixing it with an exclamation mark (!). 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.
ppp.Filter(4) ppp.Filter(4) ssrr Strict Source Routing is used to route the internet datagram based on information supplied by the source. srcrt Either Loose Source Routing or Strict Source Routing. any Any IP option - could even match the No Operation option.
ppp.Filter(4) ppp.Filter(4) pass !nntp !telnet/syn/recv # Don’t allow any packets from network whose prefix matches # prefix cafe.
ppp.Filter(4) # # # # ppp.Filter(4) Only these messages will have headers or contents logged, unless higher-level debugging is set: log 3/icmp 11/icmp 12/icmp/trace telnet/syn ftp/syn smtp/syn/terminus.netsys.
ppp.Filter(4) ppp.Filter(4) pass !x11/syn/send which is much more readable. A list of TCP and UDP service numbers and names, selected from the Assigned Numbers RFC, is available in Examples/services.ex. AUTHOR ppp.Filter was developed by HP. SEE ALSO pppd(1), ppp.Auth(4), ppp.Devices(4), ppp.Dialers(4), ppp.Keys(4), ppp.Systems(4), services(4). RFC 791, RFC 792, RFC 1055, RFC 1548, RFC 1332, RFC 1122, RFC 1144, RFC 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 pppd command does not support the gw-crypt option; customers 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) speed field is 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). EXAMPLES 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.42/V.
pppoec.conf(4) pppoec.conf(4) NAME pppoec.conf - PPPoE (Point to Point Protocol over Ethernet) client configuration file DESCRIPTION pppoec.conf is the configuration file for the pppoec daemon. This file is read by pppoec to initialize the client. The default file is /etc/ppp/pppoec.conf. Note that, you cannot run pppoec without this configuration file. Each entry in the pppoec.conf file is separated by a new line. Blank lines and lines that begin with # are ignored. Parameters pppoec.
pppoerd.conf(4) pppoerd.conf(4) NAME pppoerd.conf - PPPoE (Point to Point Protocol over Ethernet) relay configuration file DESCRIPTION pppoerd.conf is the configuration file for the pppoerd daemon. This file is read by pppoerd to initailize the relay. The default file is /etc/ppp/pppoerd.conf. Note that, you cannot run pppoerd without this configuration file. Each entry in the pppoerd.conf file is separated by a new line. Blank lines and lines that begin with # are ignored. Parameters pppoerd.
pppoesd.conf(4) pppoesd.conf(4) NAME pppoesd.conf - PPPoE (Point to Point Protocol over Ethernet) server configuration file DESCRIPTION pppoesd.conf is the configuration file for the pppoesd daemon. This file is read by pppoesd to initialize the server. The default file is /etc/ppp/pppoesd.conf. You can use this file to set parameters for each network interface used by pppoesd during PPPoE sessions. Each entry in the pppoesd.
privgrp(4) privgrp(4) NAME privgrp() - format of privileged values SYNOPSIS #include DESCRIPTION setprivgrp() sets a mask of privileges, and getprivgrp (2) returns an array of structures giving privileged group assignments on a per-group-ID basis (see getprivgrp (2)). setprivgrp() associates a kernel capability with a group ID. This allows subletting of superuser-like privileges to members of a particular group or groups.
privgrp(4) privgrp(4) SEE ALSO getprivgrp(1), setprivgrp(1M), chown(2), getprivgrp(2), lockf(2), mpctl(2), plock(2), pset_create(2), rtprio(2), rtsched(2), serialize(2), setgid(2), setuid(2), shmctl(2).
profile(4) profile(4) NAME profile - set up user’s environment at login time DESCRIPTION If the file /etc/profile exists, it is executed by the shell for every user who logs in. The file /etc/profile should be set up to do only those things that are desirable for every user on the system, or to set reasonable defaults. If a user’s login (home) directory contains a file named .profile , that file is executed (via the shell’s exec .profile ) before the session begins. .
proto(4) proto(4) NAME proto - prototype job file for at SYNOPSIS /var/adm/cron/.proto /var/adm/cron/.proto.queue DESCRIPTION When a job is submitted to at or batch , the job is constructed as a POSIX shell script (see at(1)). The job file is created in /var/spool/cron/atjobs as follows: • at creates a header describing the job as an at job or a batch job. at jobs submitted to all queues other than queue a are listed as batch jobs. The header is: : at job for an at job, or : batch job for a batch job.
protocols(4) protocols(4) NAME protocols - protocol name database 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) (TO BE OBSOLETED) 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.
prpwd(4) prpwd(4) (TO BE OBSOLETED) u_succhg This field is a time_t value that indicates the time of the last successful password change. This field should only be set by programs that can be used to change the account password. u_unsucchg This field is a time_t value that indicates the time of the last unsuccessful password change. This field should only be set by programs that can be used to change the account password.
prpwd(4) prpwd(4) (TO BE OBSOLETED) u_maxtries This field specifies the maximum number of consecutive unsuccessful login attempts to the account that are permitted until the account is locked. u_lock This flag field is used to administratively lock an account. A user cannot login to a locked account. Notes The getprpwent(3) routines are used to parse the protected password database files into a structure that can used by programs.
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, or user/host entries in the LDAP directory.
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 .
ramd.conf(4) ramd.conf(4) NAME ramd.conf - Route Administration Manager Daemon (RAMD) configuration file SYNOPSIS /etc/ramd.conf DESCRIPTION ramd.conf is the configuration file for the Route Administration Manager daemon (RAMD) for IPv6. This file comprises of configuration statements that configures ramd , ripngd , bgpd and isisd . ripngd , bgpd , and isisd are referred to as routing daemons. Upon startup, the daemons read this configuration file.
ramd.conf(4) import export ramd.conf(4) Specifies routes to be imported. Specifies routes to be exported. RAMD Global Configuration Autonomous System Statement The as sets the autonomous system number of this router to be autonomous system. This option is required if BGP is in use. The AS number is assigned by the Network Information Center (NIC). The syntax of the as configuration statement is as follows: as asnum ; This autonomous system appears only once in an AS path.
ramd.conf(4) ramd.conf(4) on polls the kernel routing table, periodically. off disables polling of the kernel routing table. By default, route polling is disabled. interval poll-interval ; Specifies how often the kernel routing table is scanned for modifications. The default poll interval is 30 seconds. By default, route polling is disabled.
ramd.conf(4) ramd.conf(4) The preference is not used to control the selection of routes within an Interior Gateway Protocol. This is accomplished automatically by the protocol based on the metric value. Each route has only one preference value associated with it, even though the preferences can be set at many places in the configuration file. The last or the most specific preference value set for a route is the value used. The route with smallest preference value is the active route.
ramd.conf(4) ramd.conf(4) If ramd is configured to reject redirects, that is if noredirect option is specified in the redirect configuration statement, it checks whether the kernel routing table is modified by the redirect message. If the kernel routing table is modified, ramd deletes the redirect route and restores the previous route that was modified by the redirect message. By default, ramd ignores the redirect messages.
ramd.conf(4) ramd.conf(4) where the following means: filter-name Specifies the unique name of the filter. filter-name must be a string and the length must not exceed 32 characters. prefix prefixlength ; prefix specifies the destination network address, and prefixlength specifies the valid number of bits in the destination network address. host host-address ; Specifies the host to configure and the destination host address. all; Specifies to filter all the valid IPv6 address.
ramd.conf(4) ramd.conf(4) all Install static, RIPng and BGP routes in the kernel routing table. route-filter-name Specifies the route filter associated with this import policy. allow Specifies that these routes provided in the route filter must be installed in the routing table. restrict Specifies that these routes must not be installed in the routing table. These routes are not exported to other protocols. By default, the routing daemons import routes to the ramd daemon.
ramd.conf(4) • ramd.conf(4) RIPng routers run as a daemon process. RIPng protocol section of the RAMD configuration file, /etc/ramd.conf, can be used to configure the RIPng daemon. rdc is a Command Line Interface (CLI) utility that controls the operations of the RIPng daemon. The CLI utility, ram_monitor , can be used to monitor the RIPng information. Enabling RIPng The RAMD configuration file enables or disables the RIPng protocol.
ramd.conf(4) dynamic both ramd.conf(4) Specifies that the RIPng router propagates only the dynamic routes. Specifies that the RIPng router propagates both static and dynamic routes. Propagation of Sitelocal Routes for RIPng The sitelocal statement specifies if site-local address can be propagated to another system or not. The syntax of the sitelocal configuration statement is as follows: sitelocal (allow |restrict ); where: allow Specifies that propagation of site-local routes is allowed.
ramd.conf(4) ramd.conf(4) where: prefix prefixlength Specifies the routes that can be aggregated and its prefix length. preference preference-value Specifies the preference value of the aggregate route. By default, the value is 130. restrict Specifies the route that ripngd must not aggregate.
ramd.conf(4) nostamp all no ramd.conf(4) Specifies that trace messages must not have the time stamp information. Traces iflist , request , policy , function , and timer information. No tracing is done. By default, no tracing is done. Gateway Filters Configuration for RIPng In the RIPng section of the RAMD configuration file, you can specify the gateway filter configuration that controls the transmission and reception of RIPng updates.
ramd.conf(4) ramd.conf(4) Associating a Profile with an Interface for RIPng The profile statement associates a profile on a particular interface. If the profile id is not specified, a default profile (id 0) is used. The syntax of the profile configuration statement is as follows: profile id ; where id specifies the profile ID on a particular interface. Route Filtering Based on Interface for RIPng You can specilfy the list of route filters for a specific interface.
ramd.conf(4) ramd.conf(4) Using ram_monitor for BGP ram_monitor can be used to monitor the BGP daemon. The BGP section in the RAMD configuration file provides a directive to specify the CLI port number. cliport port-number ; bgpd listens for ram_monitor connection on port-number. If the CLI port number is not specified, bgpd does not provide CLI service. Maximum Routes for BGP The maxroutes statement configures the maximum routes that bgpd can store in its routing table.
ramd.conf(4) both ramd.conf(4) Specifies bgpd to install both less specific and more specific routes. Route Filtering for BGP For BGP, you can configure the update filter. bgpd applies this filter on incoming and outgoing update messages. There can be many route_filter configuration statements. If no filter is configured, filter policies are not applied to the BGP packets.
ramd.conf(4) ramd.conf(4) Local Preference (LP) for BGP bgpd uses the defaultlocalpref configuration statement to set the preference value: defaultlocalpref preference-value ; where preference-value specifies the default LP value. The BGP section in the RAMD configuration file specifies the value for local preference attribute. bgpd uses the localpref configuration to set preference value based on autonomous system (AS) number, AS path or prefix.
ramd.conf(4) ramd.conf(4) prefix prefixlength Specifies the MED value for the route prefix. aspath aslist Specifies the MED value if the update message contains the specified list of AS numbers. dir (in|out ) Specifies the MED value for the incoming or outgoing update messages. By default, bgpd specifies the MED value for the incoming update messages. metricvalue metricvalue Specifies the metric value for the MED. override |inherit Specifies that the MED value must override or inherit.
ramd.conf(4) ramd.
ramd.conf(4) ramd.conf(4) multihop (on|off ); Specifies the multihop feature for a peer. Multihop must be enabled for indirectly connected external peers. By default, multihop is disabled. nexthop-self (on|off ); Specifies whether the next hop address is its own address or third party address in the update message for a peer. By default, nexthop-self is disabled. preference preference-value ; Specifies the preference value for BGP routes learned from the peer.
ramd.conf(4) ramd.
ramd.conf(4) ramd.conf(4) peer host-address [up|down ] [if ifname] {... }; where: peer host-address up|down Specifies the peer address. Specifies the administrative status of the peer. The configuration statements specified in this peer configuration statement overrides the group configuration statements except for minrtadvtime , localas and minasorgtime configuration statements. metricout configuration overrides for external peer.
ramd.conf(4) ramd.conf(4) System Level for IS-IS The level statement in the IS-IS section of the configuration file defines the level of the interface: level (l1|l2|both ); specifies the IS-IS level of the interface. By default, this value is both . Maximum Areas for IS-IS The maxareaddr statement configures the maximum area address in a system: maxareaaddr num ; where num specifies the maximum area addresses supported by IS-IS. By default, this value is 3.
ramd.conf(4) lspbufsize ramd.conf(4) Specifies the origination buffer size. By default, this value is 1492. Sitelocal Configuration for IS-IS The sitelocal statement is used to let isisd allow or restrict sending site-local address in its route updates. By default, IS-IS does not send site-local addresses in its route updates. The syntax of the sitelocal configuration statement is as follows: sitelocal (allow |restrict ) ; where: allow Specifies isisd to send site-local address in its route updates.
ramd.conf(4) ramd.conf(4) [metric metricvalue [level (l1 |l2 |both )];] [passive (on|off );] [priority prioritylevel [level (l1 |l2 |both )]; [extdomain (true |false );]}; where: enable |disable ; Enables or disables isisd . By default, this value is disable . smallhellos (on|off ); Specifies to send unpadded hellos on the interface. By default, this value is off . auth (simple ... | none ); Specifies the authentication type and authentication key for the interface. By default, this value is none .
ramd.conf(4) l1 l2 both ramd.conf(4) Specifies to enter overload state for L1. Specifies to enter overload state for L2. Specifies to enter overload state for L1 and L2. Route Leaking for IS-IS The following configuration specifies that IS-IS can leak L2 reachability information into L1 domain. By default, this value is off . The syntax of the l2tol1leak configuration statement is as follows: l2tol1leak (on|off ); where: Specifies to leak from L2 to L1.
ramd.conf(4) ramd.conf(4) SNPA-Address Specifies the Subnetwork Point of Attachment (SNPA) address. It must be one of the interface SNPA address or adjacency SNPA address. Tracing for IS-IS You can sets IS-IS tracing at protocol or event level. By default, no tracing is done. The following specifies the events to be traced. traceoptions trace-options ; where the options are separated by commas without any space between them. The valid trace options are: no all function Disables tracing.
ramd.conf(4) ramd.conf(4) maxroutes numb-of-routes ; where numb-of-routes specifies the maximum routes. By default, this value is 10000. Maximum Adjacency for IS-IS The following statement specifies the maximum adjacency that IS-IS can support. The syntax of the maxadj configuration statement is as follows: maxadj adjnum; where adjnum specifies the maximum adjacencies. By default, this value is 255. Maximum LSP for IS-IS The following statement specifies maximum LSPs that IS-IS can support.
ramd.conf(4) ramd.conf(4) A RIPng Example The following is the configuration to run ripngd with the listener mode on the lan0 interface: ripng on { admin up; cliport 15000; interface lan0 { noripout; }; }; A BGP Example The following is the configuration to run bgpd to establish BGP sessions with external peer group members and exchange IPv6 reachability information: as 200; routerid 10.4.7.
ramd.conf(4) ramd.conf(4) cliport 10501; area "49:00:01"; level both; partition yes; systemid "AB:00:00:00:00:00"; traceoptions "/tmp/isisd.log" size 1000 k files 3; traceoptions packets; interface lan1 { enable; }; }; The sample file gives an example to configure IS-IS as a L1L2 router and enable IS-IS on lan1 interface. The configuration file enables partition repair support. An area becomes partitioned as a result of failure of one or more links in the area.
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, that is, 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) (braces) (braces star) {...}+ (braces plus) <...
rcsfile(4) rcsfile(4) All nodes whose numbers consist of 2n fields (n>=2) (for example, 3.1.1.1, 2.1.2.2, etc.) are linked as follows. All nodes whose first (2n)-1 number fields are identical are linked through the next field in order of increasing numbers. For each such sequence, the node whose number is identical to the first 2(n-1) number fields of the deltas on that sequence is called the branchpoint.
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), RFC 1535.
rmtab(4) rmtab(4) NAME rmtab - remote mounted filesystem table SYNOPSIS /etc/rmtab DESCRIPTION rmtab contains a table of filesystems that are remotely mounted by NFS clients. This file is maintained by mountd(1M), the mount daemon. The data in this file should be obtained only from mountd(1M) using the MOUNTPROC_DUMP remote procedure call. The file contains a line of information for each remotely mounted filesystem.
rndc.conf(4) rndc.conf(4) (BIND 9.3) NAME rndc.conf - rndc configuration file DESCRIPTION rndc.conf is the configuration file for rndc , the BIND 9 name server control utility. This file has a structure and syntax similar to the named configuration file, named.conf . The standard (default) rndc configuration file is located at /etc/rndc.conf. The standard (default) named configuration file is located at /etc/named.conf. Syntax The syntax of the rndc.conf file is much simpler than that of the named.
rndc.conf(4) rndc.conf(4) (BIND 9.3) C: C++: UNIX: /* comment */ // to end of line # to end of line Name Server Configuration The name server must be configured to accept rndc connections and to recognize the key specified in the rndc.conf file, using the controls statement in named.conf . WARNINGS Currently, there is no way to specify the port on which rndc must run. EXAMPLES Example 1 Here is a sample rndc.
rpc(4) rpc(4) NAME rpc - rpc program number data base SYNOPSIS /etc/rpc DESCRIPTION File /etc/rpc contains user-readable names that can be used in place of RPC program numbers. Each line has the following information: • • • Name of server for the RPC program RPC program number Aliases Items are separated by any number of blanks and tab characters. A # anywhere in the file indicates a comment extending to the end of that line. EXAMPLES Here is an example of an /etc/rpc file: # # rpc 12.
rtradvd.conf(4) rtradvd.conf(4) NAME rtradvd.conf - configuration file for router advertisement daemon DESCRIPTION This file describes the information used by rtradvd(1M) when constructing IPv6 router advertisement packets for a specific interface as specified by RFC 2461 ("Neighbor Discovery for IP Version 6"). This file is read by rtradvd at initialization time or upon reception of signal SIGHUP .
rtradvd.conf(4) rtradvd.conf(4) DEFAULT: off AdvOtherConfigFlag on |off Enables (on) or disables (off ) the setting of the "Other Stateful Configuration" flag in Router Advertisements. DEFAULT: off AdvLinkMTU integer Specifies the value to be placed in MTU option sent by the router. A value of zero means unspecified. When set to 0, rtradvd does not include the MTU option in Router Advertisements. It can not be greater than the maximum allowed MTU for a specific interface.
rtradvd.conf(4) rtradvd.conf(4) DEFAULT: 0 AdvIntervalOpt on |off Mobile IPv6 option. Enables (on) or disable (off ) the sending of Advertisement Interval Option in Router Advertisement messages. If this option is included in the message, the minimum limits specified by Mobile IPv6 extension for MinRtrAdvInterval and MaxRtrAdvInterval can be used.
rtradvd.conf(4) rtradvd.conf(4) AdvSendAdvertisement on; prefixinfo 2008:0:0:6::/64 { AdvValidLifetime 70100; AdvPreferredLifetime 50200; }; }; Example 1 specifies that the daemon should send Router Advertisement messages on both lan1 and lan2 . AdvSendAdvertisement must be on (the default is off ). The AdvCurHopLimit is set to 32 for both interfaces (default value is 64). The AdvRouterLifetime for the second interface is set to 0.
rtradvd.conf(4) rtradvd.conf(4) { AdvRouterAddress on; }; }; interface lan2 { prefixinfo 2008:0:0:6::9/64 { AdvRouterAddress on; AdvPreferredLifetime 18000; }; }; In this example, the Mobile IPv6 options (AdvHomeAgentFlag, AdvHomeAgentLifetime, AdvHomeAgentPreference) will be included in the Router Advertisement messages. AdvRouterAddress is turned on to also advertise the global address of the router on lan1 and lan2 .
sccsfile(4) sccsfile(4) NAME sccsfile - format of SCCS file DESCRIPTION An SCCS file is an ASCII file consisting of six logical parts: checksum delta table user names flags body Sum of all characters in the file except the first line. Contains information about each delta. Login names and/or numerical group IDs of users who are allowed to add deltas. Definitions of internal keywords. comments Arbitrary descriptive information about the file. Actual text lines intermixed with control lines.
sccsfile(4) Flags sccsfile(4) Keywords used internally (see admin(1) for more information on their use).
sccsfile(4) sccsfile(4) Type Represented By: insert delete end @I DDDDD @D DDDDD @E DDDDD The digit string is the serial number corresponding to the delta for the control line. WARNINGS SCCS files can be any length, but the number of lines in the text file itself cannot exceed 99,999 lines. SEE ALSO admin(1), delta(1), get(1), prs(1).
sd(4) sd(4) NAME sd - all objects that Software Distributor (SD) uses, their attributes and storage formats 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) Vendor-Defined Attributes You can create your own software attributes when packaging software. Keywords in a product specification file that are not recognized by SD are preserved, along with their associated values, by being transferred to the resulting INDEX or INFO files created by swpackage or swcopy . (Refer to swpackage(4) for more information on INDEX and INFO files.) The keyword is a filename character string. The value associated with a keyword is processed as an attribute_value.
sd(4) sd(4) 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 vendor objects category objects c
sd(4) sd(4) 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) 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. contained category The object defining a category object that is associated with subsequent software objects that define a category_tag attribute.
sd(4) sd(4) 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) 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 filesets + contained subproducts
sd(4) sd(4) 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) 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) 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) 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 is_reboot is_secure is_spar
sd(4) sd(4) 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) 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) 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. superseded_by Lists what patch superseded this patch.
sd(4) sd(4) 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_integer Size 64 64 8 1024 64 2
sd(4) sd(4) 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) 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) 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 with "man".
sd(4) sd(4) 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) 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). All products with the same truncated tag will also have a unique storage directory based on the instance_id component.
sd(4) sd(4) 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) 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) 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 and prerequisites are allowed.
sd(4) sd(4) 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) 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 securenet - NIS map security file DESCRIPTION The /etc/securenets file defines networks and hosts that may access the NIS maps on a server. Each line in the file gives a network mask and a net address, each in dotted quad format. For example: 255.255.255.255 133.33.33.33 The file may have any number of netmask/net pairs. When ypserv is started on the server, it checks for the existence of /etc/securenets and reads its contents into memory if it exists.
security(4) security(4) NAME security - security defaults configuration file DESCRIPTION A number of system commands and features are configured based on certain attributes 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) userdbset -d -u username auth_failures AUTH_MAXTRIES=0 Any number of authentication retries is allowed. AUTH_MAXTRIES=N An account is locked after N+1 consecutive authentication failures. N can be any positive integer. Default value: AUTH_MAXTRIES=0 BOOT_AUTH This attribute controls whether authentication is required to boot the system into single user mode. If enabled, the system cannot be booted into single user mode until the password of an authorized user is provided.
security(4) security(4) userdbset -d -u username login_time INACTIVITY_MAXDAYS=0 Inactive accounts are not expired. INACTIVITY_MAXDAYS=N Inactive accounts are expired if there have been no logins to the account for at least N days. N can be any positive integer. Default value: INACTIVITY_MAXDAYS=0 LOGIN_TIMES This attribute restricts logins to specific time periods. Login time restrictions are based on the system’s time zone. See the discussion of time zones in the Notes section.
security(4) security(4) Default value: NOLOGIN=0 NUMBER_OF_LOGINS_ALLOWED This attribute controls the number of simultaneous logins allowed per user. Note that this is only enforced for non-root users and only applies to the applications that use session management services provided by pam_hpsec as configured in /etc/pam.conf , or those services that indirectly invoke login , such as the telnetd and rlogind commands.
security(4) security(4) changed. This value is used by the authentication subsystem during the password change process in the case where aging restrictions do not already exist for the user. The value is stored persistently and takes effect after the password change. This attribute applies only to local users and does not apply to trusted systems. The passwd -n option can be used to override this value for a specific user.
security(4) security(4) overridden by defining a per-user value in /var/adm/userdb (described in userdb(4)). UMASK= default_umask The current umask is set or restricted further with the value of default_umask. For trusted systems, the umask is also restricted so as not to exceed SEC_DEFAULT_MODE defined in /usr/include/hpsecurity.h. Default value: UMASK=0 Notes Use the functions defined in secdef(3) to read the values of the attributes defined in this file.
services(4) services(4) NAME services - service name data base DESCRIPTION The file /etc/services associates official service names and aliases with the port number and protocol the services use. For each service a single line should be present with the following information: Port numbers 0 through 1023 are assigned by RFC 1700. This RFC also lists the conventional use of various ports with numbers greater than 1023.
services.window(4) services.window(4) NAME services.window - file containing applications and their associated memory window ID DESCRIPTION The 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 , useradd , usermod , and userdel commands. Programs may use the interfaces described in the getspent(3C) manpage to access this information. These functions return a pointer to an spwd structure, which is defined in the header file.
shadow(4) shadow(4) FILES /etc/passwd /etc/shadow system password file shadow password file SEE ALSO login(1), passwd(1), pwconv(1M), pwunconv(1M), useradd(1M), userdel(1M), usermod(1M), crypt(3C), getspent(3C), putspent(3C), nsswitch.conf(4), passwd(4), security(4).
sharetab(4) sharetab(4) NAME sharetab - shared file system table DESCRIPTION sharetab in the directory /etc/dfs contains a table of local resources shared by the share command. Each line of the file consists of the following fields: pathname resource fstype specific_options description where the fields are defined as follows: pathname Path name of the shared resource. resource Symbolic name by which remote systems can access the resource. fstype File system type of the shared resource.
shells(4) shells(4) NAME shells - list of allowed login shells SYNOPSIS /etc/shells DESCRIPTION /etc/shells is an ASCII file containing a list of legal shells on the system. Each shell is listed in the file by its absolute path name. Lines or portions of lines beginning with # are assumed to be comments and are ignored. Blank lines are also ignored. AUTHOR shells was developed by HP and the University of California, Berkeley. FILES /etc/shells SEE ALSO chsh(1), ftpd(1M), getusershell(3C).
slp.conf(4) slp.conf(4) NAME slp.conf - configuration file for SLP agents SYNOPSIS /etc/slp.conf DESCRIPTION The /etc/slp.conf file contains various configuration options for the agents which include the clients that use SLP APIs, the Service Agent server and Directory agents. It determines the configuration of all the SLP agents running on that host. The SLP SA server and DA read the slp.conf file during their invocation and also when they are reconfigured by sending the SIGHUP signal.
slp.conf(4) slp.conf(4) UA Configuration The following sections of configuration properties are specified in RFC2614 and are supported for the above categories. DA configuration The configuration properties for DAs are explained in this section. net.slp.isDA A boolean indicating if the SLP server is to act as a DA. If false, slpd runs as SA server. Default is false. net.slp.DAHeartBeat A 32 bit integer giving the number of seconds for the DA heartbeat. The default is 3 hours (10800 seconds).
slp.conf(4) slp.conf(4) net.slp.traceDrop A boolean controlling printing of details when a SLP message is dropped for any reason. Default is false. net.slp.traceReg A boolean controlling dumps of all registered services upon registration and deregistration. If true, the contents of the DA or SA server are dumped after a registration or deregistration occurs. Default is false. Network Configuration Properties The properties in this section allow various network configuration properties to be set. net.
slp.conf(4) slp.conf(4) net.slp.SAAttributes A comma-separated list of parenthesized attribute/value list pairs that the SA must advertise in SAAdverts. The property must be in the SLP attribute list wire format, including escapes for reserved characters. Currently this property is ignored. UA Configuration This section describes configuration properties for the UA. These properties can be set either programmatically by the UA or in the configuration file. net.slp.
slp.reg(4) slp.reg(4) NAME slp.reg - SLP static registration file SYNOPSIS /etc/slp.reg DESCRIPTION The /etc/slp.reg file provides a mechanism for old applications which are not SLP enabled and cannot be converted, and for portably exchanging registrations between SLP implementations. This file contains a list of service registrations that are read by slpd at startup time and advertised later by slpd which can be acting either as the service agent server or the directory agent.
slp.reg(4) slp.reg(4) If the scope list contains scopes that are not in the net.slp.useScopes property (provided that property is set) or are not specified by DHCP, the API library should reject the registration and issue a warning message. AUTHOR slp.reg was developed by the Caldera Systems, Inc. SEE ALSO slpd(1M), libslp(3N), slp.conf(4), slp_syntax(7). RFC 2614, RFC 2608.
sm(4) sm(4) NAME sm, sm.bak, state - statd directory and file structures SYNOPSIS /var/statmon/sm /var/statmon/sm.bak /var/statmon/state DESCRIPTION /var/statmon/sm and /var/statmon/sm.bak are directories generated by statd (see statd(1M)). Each file in /var/statmon/sm represents one or more machines to be monitored by the statd daemon. Each file in /var/statmon/sm.bak represents one or more machines to be notified by the statd daemon upon its recovery.
snmpd.conf(4) snmpd.conf(4) NAME snmpd.conf - configuration file for the SNMP agent DESCRIPTION When invoked, the SNMP agent reads its configuration information from the /etc/SnmpAgent.d/snmpd.conf configuration file. The SNMP agent is either the snmpd(1M) (included with HP-UX) or the snmpd.ea (purchased with the HP OpenView product). The SNMP agent will not be able to reply if no values are configured in /etc/SnmpAgent.d/snmpd.conf, i.e., /etc/SnmpAgent.d/snmpd.conf is empty.
snmpd.conf(4) snmpd.conf(4) configuration file will be localSNMPID. usmUserName is user name in ASCII text. usmUserAuthProtocol is the Authentication Protocol used for sending and receiving messages, on behalf of this SNMP engine. Currently supported values are usmNoAuthProtocol and usmHMACMD5AuthProtocol. usmUserPrivProtocol is the Privacy protocol used for sending and receiving messages, on behalf of SNMP engine. Currently, no protocol is supported.
snmpd.conf(4) vacmAccessStorageType snmpd.conf(4) is nonVolatile , permanent , or readOnly . When the TAG is vacmViewTreeFamilyEntry, the format of the VALUE clause is as follows: vacmViewTreeFamilyViewName vacmViewTreeFamilySubtree vacmViewTreeFamilyMask vacmViewTreeFamilyType vacmViewTreeFamilyStorageType where: vacmViewTreeFamilyViewName is the name of the family of this view of subtrees. vacmViewTreeFamilySubtree is the object Identifier that defines the subtree.
snmpd.conf(4) snmpd.conf(4) snmpTargetAddrTMask is mask value for snmpTargetAddrTAddress. snmpTargetAddrMMS is Maximum Message Size that can be transmitted between local host and host with address snmpTargetAddrTAddress without fragmentation. Default size is 2048. When the TAG is snmpNotifyEntry, the format of the VALUE clause is as follows: snmpNotifyName snmpNotifyTag snmpNotifyType snmpNotifyStorageType where: snmpNotifyName is the ASCII text representing the name of notification.
snmpd.conf(4) snmpd.conf(4) # Specify the agent is located on the first floor # near the mens room location: 1st Floor near Mens Room # Specify Bob Jones is responsible for this agent # and his phone number is 555-2000 contact: Bob Jones (Phone 555-2000) # Create a SNMPv3 user ’v3usr’ with No Authentication Protocol. usmUserEntry localSnmpID v3usr usmNoAuthProtocol 1.3.6.1.6.3.10.1.2.
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) 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) PRODUCT SPECIFICATION FILE SYNTAX A PSF is structured as follows: [] [] [] [] ... [] [] [] [] ... [] [] ...
swpackage(4) • swpackage(4) 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. These objects and attributes can appear in any order when defining a distribution, vendor, category, product, or bundle, except that the layout_version attribute must be first.
swpackage(4) swpackage(4) 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 boolean boolean revision_string
swpackage(4) swpackage(4) 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.oldfileset oldproduct.fileset HP-UX_B.11.
swpackage(4) swpackage(4) 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) path_mapping_string Maximum length: none 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) • location applies only to installed software and refers to software installed to a location other than the default product directory. • fr and fa apply only to filesets. r , a , v , c , and l apply only to bundles and products. They are applied to the left- • most 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.
swpackage(4) swpackage(4) 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) 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. 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 .
swpackage(4) 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 swpackage(4) SD HP-UX_B.11.11_32/64 Ordered Apps prod.fs1.r=1.0,a=,v=
swpackage(4) swpackage(4) 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) 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). os_release Defines the operating system release(s) on which the product will run.
swpackage(4) swpackage(4) 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) 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) is_sparse Indicates that a fileset contains only a subset of files in the base (ancestor) fileset and that the contents are to be merged with the base fileset. The default value is false . If the is_patch attribute is true , is_sparse is also set to true for the fileset, although it can be forced to false. machine_type Defines the machine(s) on which the files will run if a fileset architecture has been defined.
swpackage(4) swpackage(4) ... exrequisites ... productB,r>=2.1 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) script which tag is being executed.) For example, the following specification defines the same file for use by multiple scripts: 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 .
swpackage(4) swpackage(4) the configure script. unpostinstall Defines the installation pre-restore script executed by swinstall . A fileset script is executed immediately before the fileset files are restored if there is an error and the autorecover_product option is set to true. Note that unpostinstall scripts are supported for filesets only. It should undo the steps taken by the postinstall script. unpreinstall Defines the installation post-restore script executed by swinstall .
swpackage(4) swpackage(4) SW_CONTROL_TAG Holds the tag name of the control_file being executed. When packaging software, you can define a physical name and path for a control file in a depot. This lets you define the control_file with a name other than its tag and lets you use multiple control file definitions to point to the same file. A control_file can query the SW_CONTROL_TAG variable to determine which tag is being executed.
swpackage(4) swpackage(4) Directory Mapping The directory source[=destination] keyword defines a source directory under which subsequently listed files are located. In addition, the user can map the source directory to a destination directory under which the packaged files will be installed. For example, the definition: directory ./commands = /usr/sbin causes all files from the ./commands directory to have the prefix /usr/sbin when installed.
swpackage(4) swpackage(4) -o [owner[,]][ uid] Defines the destination file’s owner name and/or or uid. If only the owner is specified, the owner and uid attributes are set for the destination file object, based on the packaging host’s /etc/passwd . If only the uid is specified, it is set as the uid attribute for the destination object and no owner name is assigned. If both are specified, each sets the corresponding attribute for the file object.
swpackage(4) swpackage(4) By specifying a umask , the user can set a default mode for executable files, non-executable files, and directories. (A specific mode can be set for any file, as described above.) -o [owner[,]][ uid] Defines the destination file’s owner name and/or or uid (as defined above). -g [group[,]][ gid] Defines the destination file’s group name and/or or gid (as defined above). -t type Defines the destination file’s type (as defined above).
swpackage(4) swpackage(4) directory / is_locatable false # Create a product script which executes during the swremove # analysis phase. (This particular script returns an ERROR, # which prevents the removal of the SD product.) checkremove scripts/checkremove.
swpackage(4) end swpackage(4) # SD Example File Specifications The following examples illustrate the use of the directory and file keywords: Include all files under ./commands/ , to be rooted under /usr/sbin/ : directory ./commands=/usr/sbin file * Include only certain files under ./commands/ and ./nls , to be rooted under /usr/sbin/ and /usr/lib/nls/C/: directory ./commands=/usr/sbin file sbin/swinstall file sbin/swcopy ... directory ./nls=/usr/lib/nls/C/ file swinstall.cat file swremove.cat ...
swpackage(4) swpackage(4) for destination file objects based on existing source files. (Meaning the mode, owner/uid, group/gid are set based on the source file, unless specific overrides are specified for a destination file.) WARNINGS Some releases of swpackage do not work correctly with the -t type construct in a PSF. The swpackage program in the HP-UX 11i v1 (11.11) PHCO_34295 patch, 11i v1 (11.11) OEUR available after the patch, 11i v2 (11.
symlink(4) symlink(4) NAME symlink - symbolic link DESCRIPTION A symbolic (or soft ) link is a file whose name indirectly refers (points) to a relative or absolute path name. During path name interpretation, a symbolic link to a relative path name is expanded to the path name being interpreted, and a symbolic link to an absolute path name is replaced with the path name being interpreted. Thus, given the path name /a/b/c/d : If c is a symbolic link to a relative path name such as ..
system(4) system(4) NAME system - system description configuration files DESCRIPTION The HP-UX system description file describes kernel configuration information used by the kconfig and mk_kernel commands. The system description file consists of the following information: • A line specifying the version of the system file. • The list of packaged and traditional kernel modules to be configured. • Planned values for system tunable parameters, and other system-wide configuration information.
system(4) system(4) selects the driver for SCSI disk drives. module pseudodrv loaded 1.0.[3E0D0C96] dynamically loads the module pseudodrv . System files may also contain lines that are used to: • • • • define the swap device define the dump device(s) provide an explicit binding a driver to a hardware path define status and values of selected system parameters. Lines are constructed as indicated below for each category.
system(4) • system(4) Explicit Device Driver Bindings One or more driver to hardware path specifications is allowed. If a driver statement is provided, the specified software module is forced into the kernel I/O system at the given hardware path. This can be used to make the system recognize a device that could not be recognized automatically. driver hw_path driver_name Bind the driver into the kernel I/O system at the given hardware path.
tar(4) tar(4) NAME tar - format of tar tape archive DESCRIPTION The header structure produced by tar (see tar(1)) is as follows (the array size defined by the constants is shown on the right): struct { char char char char char char char char char char char char char char char char } dbuf; name[NAMSIZ]; (100) mode[MODE_SZ]; (8) uid[UID_SZ]; (8) gid[GID_SZ]; (8) size[SIZE_SZ]; (12) mtime[MTIME_SZ]; (12) chksum[CHKSUM_SZ]; (8) typeflag; linkname[NAMSIZ]; (100) magic[MAGIC_SZ]; (6) version[VERSION_SZ]; (2)
tcpd.conf(4) tcpd.conf(4) NAME tcpd.conf - configuration file for tcpd DESCRIPTION When inetd invokes tcpd for a service, it will read /etc/tcpd.conf and perform access control checks (see tcpd(1M)). Each line in the file is treated either as a comment or as configuration information. Commented lines begin with #. Uncommented lines contain two required fields, key and value. The fields are separated by tabs and/or spaces. A line can be continued if it terminates with a backslash (\).
tcpd.conf(4) rfc931_timeout tcpd.conf(4) 0 To make tcpd to allow a host on reverse lookup failure and process that host as PARANOID , in ACLs: on_reverselookup_fail allow To set the extended logging option: log_level extended AUTHOR tcpd.conf was developed by the Hewlett-Packard. SEE ALSO inetd(1M), tcpd(1M).
term(4) term(4) NAME term - format of compiled term file SYNOPSIS term DESCRIPTION Compiled terminfo descriptions are placed under the directory /usr/share/lib/terminfo. In order to avoid a linear search of a huge HP-UX system directory, a two-level scheme is used: /usr/share/lib/terminfo/c /name where name is the name of the terminal, and c is the first character of name. Thus, hp110 can be found in the file /usr/share/lib/terminfo/h/hp110.
term(4) term(4) 110|hp110|hp110a portable computer, am, xhp, da, db, mir, cols#80, lines#16, lm#0, cbt=\Ei, bel=ˆG, cr=\r, tbc=\E3, clear=\E&a0y0C\EJ, el=\EK, ed=\EJ, hpa=\E&a%p1%dC, cup=\E&a%p1%dy%p2%dC, cud1=\EB, cub1=\b, cuf1=\EC, cuu1=\EA, cvvis=\E&j@, dch1=\EP, dl1=\EM, smir=\EQ, smso=\E&dB, sgr0=\E&d@, rmir=\ER, rmso=\E&d@, is2=\E&j@, if=/usr/share/lib/tabset/stdcrt, il1=\EL, kbs=\b, kcud1=\EB, khome=\Eh, kcub1=\ED, kcuf1=\EC, kcuu1=\EA, rmkx=\E&s0A, smkx=\E&s1A, vpa=\E&a%p1%dY, ind=\n, hts=\E1, ht=
term_c(4) term_c(4) NAME term_c: term.h, TERM - 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) 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_alt_charset_mode
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) 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 t 480 term_c(4) kcan kt
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) 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_address micro_up
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/?/* DESCRIPTION The requirements in this manpage are in effect only for implementations that claim Enhanced Curses compliance.
terminfo(4) terminfo(4) (ENHANCED CURSES) shows the format of a terminfo source file: 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 ; Note (1) An ALIAS that begins in column one. This is handled by the lexical analyzer. Note (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) information to determine how properly to operate the current terminal. In addition, implementations return any of the current terminal’s capabilities when the application calls the query functions listed in tgetent() (in the cases where the following tables list a Termcap code) and tigetflag() (see tgetent(3X) and tigetflag(3X)).
terminfo(4) terminfo(4) (ENHANCED CURSES) Booleans Variable auto_left_margin auto_right_margin back_color_erase can_change ceol_standout_glitch col_addr_glitch cpi_changes_res Cap name bw am bce ccc xhp xhpa cpix Term cap bw am ut cc xs YA YF cr_cancels_micro_mode dest_tabs_magic_smso eat_newline_glitch erase_overstrike generic_type get_mouse hard_copy hard_cursor has_meta_key has_print_wheel crxm xt xenl eo gn getm hc chts km daisy YB xt xn eo gn Gm hc HC km YC has_status_line hs hue_lightness_satu
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 Cap name bitwin bitype bufsz btns cols spinh spinv it lh lw lines lm Term cap Yo Yp Ya BT co Yc Yb it lh lw li lm max_attributes ma ma magic_cookie_glitch xmc sg max_colors max_micro_address max_micro_jump max_pairs maximum_windows micro_col_size micro_line_size no_color_video num_la
terminfo(4) terminfo(4) (ENHANCED CURSES) Strings (part 1 of 3) Term cap Description ac Graphic charset pairs aAbBcC S8 Alternate escape for scancode emulation (default is for VT100) back_tab cbt bt Back tab bell bel bl Audible signal (bell) bit_image_carriage_return bicr Yv Move to beginning of same row bit_image_newline binel Zz Move to next row of the bit image bit_image_repeat birep Xy Repeat bit-image cell #1 #2 times carriage_return cr cr Carriage return change_char_pitch cpi ZA Change number of cha
terminfo(4) terminfo(4) (ENHANCED CURSES) t 492 end_bit_image_region enter_alt_charset_mode 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_
terminfo(4) terminfo(4) (ENHANCED CURSES) fixed_pause flash_hook flash_screen form_feed from_status_line goto_window hangup init_1string pause hook flash ff fsl wingo hup is1 PA fh vb ff fs WG HU i1 init_2string is2 is init_3string is3 i3 init_file init_prog initialize_color initialize_pair if iprog initc initp if iP IC Ip insert_character insert_line insert_padding ich1 il1 ip ic al ip Pause for 2−3 seconds Flash the switch hook Visible bell (may move cursor) Hardcopy terminal page eject R
terminfo(4) terminfo(4) (ENHANCED CURSES) 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 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 t 494 k
terminfo(4) terminfo(4) (ENHANCED CURSES) 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 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_
terminfo(4) terminfo(4) (ENHANCED CURSES) key_stab key_sundo key_suspend key_undo key_up kT !3 &7 &8 ku Sent Sent Sent Sent Sent Cap name rmkx smkx lf0 lf1 lf2 lf3 lf4 lf5 lf6 lf7 lf8 lf9 lf10 fln rmln smln meml memu rmm smm mhpa mcud1 mcub1 mcuf1 mvpa mcuu1 minfo nel porder oc op pad dch dl cud mcud ich indn il cub mcub cuf mcuf rin cuu mcuu pctrm pfkey Term cap ke ks l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 la Lf LF LO ml mu mo mm ZY ZZ Za Zb Zc Zd Mi nw Ze oc op pc DC DL DO Zf IC SF AL LE Zg RI Zh SR UP Zi S6
terminfo(4) terminfo(4) (ENHANCED CURSES) pkey_local pkey_plab pfloc pfxl pl xl pkey_xmit plab_norm print_screen prtr_non prtr_off prtr_on pulse quick_dial pfx pln mc0 mc5p mc4 mc5 pulse qdial px pn ps pO pf po PU QD 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_char_set set0_des_seq set1_des_seq set2_des_seq set3_des_seq set_a_attributes set_a_backg
terminfo(4) terminfo(4) (ENHANCED CURSES) 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 smgtp wind sbim scsd rbim rcsd subcs supcs ht docr tsl tone u0 u1 u2 u3 u4 u5 u6 u7 u8 u9 uc hu wait xoffc xonc zerom Zp wi Zq Zr Zs Zt Zu Zv ta
terminfo(4) terminfo(4) (ENHANCED CURSES) sgr0=\E[mˆO, smacs=ˆN, smir=\E[4h, smln=\E[p, smso=\E[7m, smul=\E[4m, tsl=\E7\E[25;%i%p1%dx, Types of Capabilities in the Sample Entry The sample entry shows the formats for the three types of terminfo capabilities: boolean, numeric, and string. All capabilities specified in the terminfo source file must be followed by commas, including the last capability in the source file.
terminfo(4) terminfo(4) (ENHANCED CURSES) Notation ^x \a \b \E or \e \f \l \n \r \s \t \ˆ \\ \, \: \0 \nnn Represents Character Control-x (for any appropriate x) Alert Backspace An ESCAPE character Form feed Linefeed Newline Carriage return Space Tab Caret (ˆ) Backslash (\) Comma (,) Colon (:) Null Any character, specified as three octal digits (See the "X/Open System Interface Definitions, Issue 4, Version 2" specification, "General Terminal Interface".
terminfo(4) terminfo(4) (ENHANCED CURSES) cr and lf it may still be possible to craft a working nel out of one or both of them. These capabilities suffice to describe hardcopy and screen terminals.
terminfo(4) terminfo(4) (ENHANCED CURSES) %? c1 %t b1 %e c2 %t b2 %e c3 %t b3 %e c4 %t b4 %e b5 %; ci are conditions; bi are bodies. If the "-" flag is used with "%[doxXs]", then a colon must be placed between the "%" and the "-" to differentiate the flag from the binary "%-" operator. For example: "%:-16.16s". Consider the Hewlett-Packard 2645, which, to get to row 3 and column 12, needs to be sent \E&a12c03Y padded for 6 milliseconds.
terminfo(4) terminfo(4) (ENHANCED CURSES) from the first position on the line to be deleted. Versions of il1 and dl1 which take a single argument and insert or delete that many lines can be given as il and dl. If the terminal has a settable destructive scrolling region (like the VT100) the command to set this can be described with the csr capability, which takes two arguments: the top and bottom lines of the scrolling region. The cursor position is, alas, undefined after using this command.
terminfo(4) terminfo(4) (ENHANCED CURSES) needs to be placed in for dch1 to work). A command to erase n characters (equivalent to outputting n blanks without moving the cursor) can be given as ech with one argument. Highlighting, Underlining, and Visible Bells Your device may have one or more kinds of display attributes that allow you to highlight selected characters when they appear on the screen.
terminfo(4) terminfo(4) (ENHANCED CURSES) tparm() Argument p1 p2 p3 p4 p5 p6 p7 p8 p9 Attribute none standout underline reverse blink dim bold invis protect altcharset Escape Sequence \E[0m \E[0;4;7m \E[0;3m \E[0;4m \E[0;5m \E[0;7m \E[0;3;4m \E[0;8m not available ˆO (off) ˆN (on) Note that each escape sequence requires a 0 to turn off other modes before turning on its own mode. Also note that, as suggested above, standout is set up to be the combination of reverse and dim.
terminfo(4) terminfo(4) (ENHANCED CURSES) Strings to program function keys can be specified as pfkey, pfloc, and pfx. A string to program screen labels should be specified as pln. Each of these strings takes two arguments: a function key identifier and a string to program it with. pfkey causes pressing the given key to be the same as the user typing the given string; pfloc causes the string to be executed by the terminal in local mode; and pfx causes the string to be transmitted to the computer.
terminfo(4) terminfo(4) (ENHANCED CURSES) rc. The status line is normally assumed to be the same width as the rest of the screen (that is, cols). If the status line is a different width (possibly because the terminal does not allow an entire line to be loaded) the width, in columns, can be indicated with the numeric argument wsl. Line Graphics If the device has a line drawing alternate character set, the mapping of glyph to character would be given in acsc.
terminfo(4) terminfo(4) (ENHANCED CURSES) • Hewlett-Packard-style In the HP method, the application cannot define the foreground independently of the background, or vice-versa. Instead, the application must define an entire color-pair at once. Up to M colorpairs, made from 2*M different colors, can be defined this way. 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.
terminfo(4) terminfo(4) (ENHANCED CURSES) Attribute WA_STANDOUT WA_UNDERLINE WA_REVERSE WA_BLINK WA_DIM WA_BOLD WA_INVIS WA_PROTECT WA_ALTCHARSET WA_HORIZONTAL WA_LEFT WA_LOW WA_RIGHT WA_TOP WA_VERTICAL Bit Position 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Decimal Value 1 2 4 8 16 32 64 128 256 512 1024 2048 4096 8192 16384 Characteristic That Sets sgr, parameter 1 sgr, parameter 2 sgr, parameter 3 sgr, parameter 4 sgr, parameter 5 sgr, parameter 6 sgr, parameter 7 sgr, parameter 8 sgr, parameter 9 sgr1, par
terminfo(4) terminfo(4) (ENHANCED CURSES) Media copy strings which control an auxiliary printer connected to the terminal can be given as: mc0 Print the contents of the screen. mc4 Turn off the printer. mc5 Turn on the printer. When the printer is on, all text sent to the terminal will be sent to the printer. A variation, mc5p, takes one argument, and leaves the printer on for as many characters as the value of the argument, then turns the printer off. The argument should not exceed 255.
terminfo(4) terminfo(4) (ENHANCED CURSES) size given by the smallest horizontal and vertical step sizes dictated by the resolution. (The cell size can be changed as will be seen later.) Many printers are capable of "proportional printing", where the horizontal spacing depends on the size of the character last printed. terminfo does not make use of this capability, although it does provide enough capability definitions to allow an application to simulate proportional printing.
terminfo(4) terminfo(4) (ENHANCED CURSES) Changing the Character/Line Pitches cpi Change character pitch cpix If set, cpi changes orhi; otherwise, changes orc lpi lpix Change line pitch If set, lpi changes orvi; otherwise, changes orl chr cvr Change steps per column Change steps per line The cpi and lpi string capabilities are each used with a single argument, the pitch in columns (or characters) and lines per inch, respectively.
terminfo(4) terminfo(4) (ENHANCED CURSES) String Capabilities for Motion mcub1 Move 1 step left mcuf1 Move 1 step right mcuu1 Move 1 step up mcud1 Move 1 step down mcub mcuf mcuu mcud Move Move Move Move N steps left N steps right N steps up N steps down mhpa mvpa Move N steps from the left Move N steps from the top The latter six strings are each used with a single argument, N. Sometimes the motion is limited to less than the width or length of a page.
terminfo(4) terminfo(4) (ENHANCED CURSES) Entering/Exiting Reverse Modes slm Reverse sense of horizontal motions rlm Restore sense of horizontal motions sum Reverse sense of vertical motions rum Restore sense of vertical motions While sense of horizontal motion is reversed: mcub1 Move 1 step right mcuf1 Move 1 step left mcub Move N steps right mcuf Move N steps left cub1 Move 1 column right cuf1 Move 1 column left cub Move N columns right cuf Move N columns left While sense of vertical motion is reversed:
terminfo(4) terminfo(4) (ENHANCED CURSES) Setting Margins smgl Set left margin at current column smgr Set right margin at current column smgb Set bottom margin at current line smgt Set top margin at current line smgbp smglp smgrp smgtp Set Set Set Set bottom margin at line N left margin at column N right margin at column N top margin at line N The last four strings are used with one or more arguments that give the position of the margin or margins to set.
terminfo(4) terminfo(4) (ENHANCED CURSES) It is assumed that enhanced printing modes are independent modes, so that it would be possible, for instance, to shadow print italicized subscripts. As mentioned earlier, the amount of motion automatically made after printing a wide character should be given in widcs. If only a subset of the printable ASCII characters can be printed as superscripts or subscripts, they should be listed in supcs or subcs strings, respectively.
terminfo(4) terminfo(4) (ENHANCED CURSES) When used with a character set number in a call to tparm(), the csnm string will produce the equivalent name. These names should be used as a reference only. No naming convention is implied, although anyone who creates a terminfo entry for a printer should use names consistent with the names found in user documents for the printer.
terminfo(4) terminfo(4) (ENHANCED CURSES) would be ,,6,5,4,3,2,1;63, equivalent to o,o,6,5,4,3,2,1;63.
terminfo(4) terminfo(4) (ENHANCED CURSES) buffer is not full. By keeping track of the characters sent to a printer, and knowing the print rate and buffer size, a program can synchronize itself with the printer. Note that most printer manufacturers advertise the maximum print rate, not the nominal print rate. A good way to get a value to put in for cps is to generate a few pages of text, count the number of printable characters, and then see how long it takes to print the text.
terminfo(4) terminfo(4) (ENHANCED CURSES) Suffix -w -am -nam -n -na -np -rv Meaning Wide mode (more than 80 columns) With automatic margins (usually default) Without automatic margins Number of lines on the screen No arrow keys (leave them in local) Number of pages of memory Reverse video Example 5410-w vt100-am vt100-nam 2300-40 c100-na c100-4p 4415-rv Variations of Terminal Definitions It is implementation-defined how the entries in terminfo may be created.
ttys(4) ttys(4) (TO BE OBSOLETED) 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) (TO BE OBSOLETED) 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/ .
tztab(4) tztab(4) NAME tztab - time zone adjustment table for date and ctime() DESCRIPTION The /usr/lib/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.
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).
userdb(4) userdb(4) NAME userdb - user database for per-user information SYNOPSIS /var/adm/userdb DESCRIPTION The user database is used for storing per-user information. It consists of the /var/adm/userdb directory and the files within it. Each file name is a two-digit hexadecimal number from 00 to ff . The directory and files are created either at installation time or by the userdbck command.
userdb(4) /etc/default/security /etc/security.dsc userdb(4) security defaults configuration file security attributes description file SEE ALSO userdbck(1M), userdbget(1M), userdbset(1M), userdb_read(3), security(4).
usermod(4) usermod(4) NAME usermod - list of home directory names DESCRIPTION /etc/default/usermod is an ASCII file that contains a list of home directory names. The usermod command checks this configuration file before changing a user’s home directory. If the user’s old home directory is listed in /etc/default/usermod, the user’s directories/files will be prevented from moving to a new home directory.
utmp(4) utmp(4) (TO BE OBSOLETED) NAME utmp, wtmp, btmp - user login record format SYNOPSIS #include #include DESCRIPTION These files, which hold user and accounting information for such commands as last , who , write , and login (see last(1), who(1), write(1), and login(1)), have the following structure as defined by
utmp(4) utmp(4) (TO BE OBSOLETED) FILES /etc/utmp /var/adm/wtmp /var/adm/btmp AUTHOR utmp , wtmp , and btmp were developed by HP and the University of California, Berkeley. SEE ALSO last(1), login(1), who(1), write(1), acctcon(1M), fwtmp(1M), utmpd(1M), getut(3C), getuts(3C), getutx(3C). STANDARDS CONFORMANCE
utmps(4) utmps(4) NAME utmps - user-accounting database SYNOPSIS #include #include DESCRIPTION File utmps contains user accounting information for all users logged onto the system. This file will be accessed by getuts(3C) only if utmpd(1M) is not running.
utmpx(4) utmpx(4) NAME utmpx - utmpx database storage file SYNOPSIS #include #include DESCRIPTION File utmpx contains user accounting information for all users logged onto the system. This file will be used instead of the utmp file, which is being depreciated.
uuencode(4) uuencode(4) NAME uuencode - format of an encoded uuencode file DESCRIPTION Files output by uuencode consist of a header line followed by a number of body lines, and a trailer line. The uudecode command ignores any lines preceding the header or following the trailer (see uuencode(1)). Lines preceding a header must not look like a header. The header line consists of the word begin followed by a space, a mode (in octal), another space, and a string which specifies the name of the remote file.
wtmps(4) wtmps(4) NAME wtmps, btmps - user login information SYNOPSIS #include #include DESCRIPTION wtmps and btmps hold user and accounting information for such commands as last , who , write , and login (see last(1), who(1), write(1), and login(1)). File btmps contains bad login entries for each invalid logon attempt. File wtmps contains a record for all logins and logouts apart from accounting records.
ypfiles(4) ypfiles(4) NAME ypfiles - Network Information Service database and directory structure DESCRIPTION Note: 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 auto.master ethers.byaddr ethers.byname group.bygid group.byname hosts.byaddr hosts.byname ipnodes.byaddr ipnodes.byname mail.aliases mail.byaddr 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 ypservers Abbreviated Mapname auto.mast ether.byad ether.byna group.bygi group.byna hosts.byad hosts.byna ip.
ypfiles(4) ypfiles(4) General NIS Mapname ASCII Source aliases /etc/mail/aliases automounter ethers /etc/auto_master * group /etc/group hosts /etc/hosts ipnodes /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 ypservers ** Standard NIS Mapname mail.aliases mail.byaddr auto.master ethers.byaddr ethers.byname group.byname group.bygid hosts.byname hosts.
