|
|
|
.netrc(4) -- login information for ftp and rexec
|
|
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 file contains password or account information for use other than for anonymous ftp, its owner must matc... |
|
.rhosts(4) -- security files authorizing access by remote hosts and users on local host
|
|
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)). The security provided by hosts.equiv i... |
|
|
a.out(4) -- assembler and link editor output
|
|
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. Programs that manipulate ELF files may use the library that elf(3E) describes. An overview of the f... |
|
acct(4) -- per-process accounting file format
|
|
Files produced as a result of calling acct() (see acct(2)) have records in the form defined by , whose contents are: typedef ushort comp_t; /* "floating point": 13-bit fraction, 3-bit exponent */ struct acct { char ac_flag; /* Accounting flag */ char ac_stat; /* Exit status */ uid_t ac_uid; /* Accounting user ID */ gid_t ac_gid; /* Accounting group ID */ dev_t ac_tty; /* control type... |
|
ar(4) -- common archive file format
|
|
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 ARMAG "!\n" /* magic string */ #define SARMAG 8 /* length of magic string */ Following the archive magic string are the archive file members. Each file member is... |
|
audeventsta(4) -- define and describe audit system events
|
|
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. name Corresponding mnemonic name: a single field separated... |
|
audit(4) -- file format and other information for auditing
|
|
Audit records are generated when users make security-relevant system calls, as well as by self-auditing processes that call audwrite() (see audwrite(2)). Access to the auditing system is restricted to superuser. Each audit record consists of an audit record header and a record body. The record header is comprised of time, process ID, error, event type, and record body length. The time refers to th... |
|
authcap(4) -- security databases for trusted systems
|
|
All security-relevant databases are stored in an ASCII format in the file system. This format is converted to binary structures by support routines described in Section 3 manual entries. This manual entry describes the format of these databases, and describes the philosophy of conversion into data structures. |
|
bootconf(4) -- boot device configuration table
|
|
This file, /stand/bootfonf, contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the Software Distributor and HP-UX kernel control scripts (fileset OS- Core.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. In rare cases when either ... |
|
btmp(4) -- utmp, wtmp, btmp entry format
|
|
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 : #define UTMP_FILE "/etc/utmp" #define WTMP_FILE "/var/adm/wtmp" #define BTMP_FILE "/var/adm/btmp" #define ut_name ut_user struct utmp { char ut_user[8]; /* User login name */ char ut_id[4];... |
|
btmps(4) -- user login information
|
|
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. These files contain utmps-like structure, the key elements of the structure are given below: c... |
|
cdnode(4) -- format of a CDFS cdnode
|
|
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. The cdnode informati... |
|
cdrom(4) -- CD-ROM background information
|
|
This manual entry provides general information on existing CD-ROM standards, terminology, data layout, and levels of support. More detailed information is available in the standard documents listed in SEE ALSO. Not all topics discussed here are supported in the current HP-UX release. Refer to the DEPENDENCIES section for details about the contents of the current release. |
|
charmap(4) -- symbolic translation file for localedef scripts
|
|
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. The charmap file has two sections: a declarations section and a character definition section. |
|
core(4) -- format of core image file
|
|
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 ... |
