umount failure on source device
The source device could not be dismounted. Since it was mounted read~only, the integrity of its file system is not at risk.
write failure
An error was encountered writing to the destination device or file.
Configuration
cannot add path, error number
An unknown error has occurred in adding the hardware path to the I/O tree. The internal error number is given. Contact your HP Field Representative.
driver does not exist
The manager specified is not configured into hpux.
driver is not a logical device manager
The manager name given is not that of a logical device manager and cannot be used for direct I/O operations.
error rewinding device
An error was encountered attempting to rewind a device.
error skipping file
An error was encountered attempting to forward~space a tape device.
negative skip count
The skip count, if specified, must be greater than or equal to zero.
no major number
The specified manager has no entry in the block or character device switch tables.
path incompatible with another path
Multiple incompatible hardware pathes have been specified.
path long
The hardware path specified contains too many components for the specified manager.
path short
The hardware path specified contains too few components for the specified manager.
table full
Too many devices have been specified to hpux.
SEE ALSO
a.out(4), boot(lM), errno(2), fsck(lM), init(lM), inittab(4), isl(lM), magic(4), pdc(lM), rdb(lM).
Hewlett-Packard Company - 9 - Version B.1, December 1986
INIT(lM) HP-UX INIT(lM)
NAME
init, telinit - process control initialization SYNOPSIS may log in on. It also controls autonomous processes required by any particular system.
Init considers the system to be in a run-level at any given time. A run-level can be viewed as a rebooted, telling it which run-level to change to.
Init is invoked inside the HP-UX system as the last step in the boot procedure. The first thing telinit command can signal init and force it to change the run-level of the system.
When attempting to boot the system, failure of init to prompt for a new run-level may be due to the fact that the device /dev /syscon is linked to a device other than the physical system tele-type (fdev/systty). If this occurs, init can be forced to relink /dev/syscon by typing a delete on the system teletype which is collocated with the processor.
When init prompts for the new run-level, the operator may enter only one of the digits 0 through 6 or the letters S or s. If S is entered init operates as previously described in SINGLE USER mode with the additional result that /dev /syscon is linked to the user's terminal line, thus making it the virtual system console. A message is generated on the physical console, /dev/systty, saying where the virtual terminal has been relocated.
When init comes up initially and whenever it switches out of SINGLE USER state to normal run
These entries are performed, providing the run-level entered matches that of the entry before any normal processing of inittab takes place. In this way any special initialization of the operating system, such as mounting file systems, can take place before users are allowed onto the system.
Hewlett-Packard Company - 1 - Version B.1, October 1986
INIT(lM) HP-UX INIT(lM)
The inittab file is scanned to find all entries that are to be processed for that run-level.
Run-level 2 is usually defined by the user to contain all of the terminal processes and daemons that are spawned in the multi-user environment.
In a multi-user environment, the inittab file is usually set up so that init will create a process for each terminal on the system.
For terminal processes, ultimately the shell will terminate because of an end-of-file either typed explicitly or generated as the result of hanging up. When init receives a child death signal, telling it that a process it spawned has died, it records the fact and the reason it died in /etc/utmp and whenever the operating system experiences a power failure.
When init is requested to change run-levels (via telinit) , init sends the warning signal (SIGTERM) to all processes that are undefined in the target run-level. [nit waits 20 seconds before forcibly terminating these processes via the kill signal (SIGKILL).
Telinit
FILES
Telinit, which is linked to /etc/init, is used to direct the actions of init. It takes a one-character argument and signals init via the kill system call to perform the appropriate action. The following arguments serve as directives to init. from which the command was executed.
Telinit can only be run by someone who is super-user or a member of group sys.
getty(lM), 10gin(1), sh(l), who(l), kill(2), inittab(4), utmp(4).
DIAGNOSTICS
If init finds that it is continuously respawning an entry from /etc/inittab more than 10 times in
Hewlett-Packard Company - 2 - Version B.1, October 1986
INIT(lM) HP-UX INIT(lM)
2 minutes, it v.rill asslL1Jle that there is 3...."1 error in the comm&id string, and generate an error llles-sage on the system console, and refuse to respawn this entry until either 5 minutes has elapsed or it receives a signal from a user init (telinit). This prevents init from eating up system resources when someone makes a typographical error in the inittab file or a program is removed that is referenced in the inittab.
Hewlett-Packard Company - 3 - Version B.1, October 1986
INST ALL (1M) HP-UX INST ALL ( 1M) and exits without further action.
If one or more directories (dirx ... ) are specified after file, those directories will be searched before the directories specified in the default list.
The meanings of the options are:
--c dira Installs a new command (file) in the directory specified by dira, only if it is not found. If it is found, install issues a message saying that the file already exists, and exits without overwriting it. May be used alone or with the -s option.
Ignores default directory list, searching only through the given directories (dirx ... ). May be used alone or with any other options other than --c and
INSTALL (1M) HP-UX INSTALL (1M)
When no directories are specified (dirx ... ), or when file cannot be placed in one of the direc-tories specified, install checks for the existence of the file /ete/syslist. If /ete/syslist exists, it is used to determine the final destination of file. If /ete/syslist does not exist, the default directory list is further scanned in order to determine where file is to be located.
The file /ete/syslist contains a list of absolute pathnames, one per line. The pathname is the "official" destination (for example /bin/eeho) of the file as it appears on a file system.
/ete/syslist serves as a master list for system command destinations. If there is no entry for file in the file /ete/syslist then the default directory list is further scanned in order to deter-mine where file is to be located.
Cross Generation
The environment variable ROOT will be used to locate the locations file (in the form
£ROOT/ete/syslist). This is necessary in the cases where cross generation is being done on a production system. Furthermore, each pathname in £ ROOT /ete/syslist is appended to $ROOT (for example, £ROOT/bin/eeho ) and used as the destination for file. Also, the default direc-tories are also appended to £ ROOT so that the default directories are actually
£ ROOT /bin,£ ROOT /UST /bin,£ ROOT jete, £ ROOT/lib, and £ ROOT /UST /lib.
The file /ete/syslist ($ROOT/etc/syslistj does not exist on a distribution tape; it is created and used by local sites.
SEE ALSO
cpset(lM), make(l).
BUGS
Install cannot create alias links for a command (for example, vi(l) is an alias link for ex(l)).
Hewlett-Packard Company - 2 - Version B.1, October 1986
ISL(lM) ISL(lM) and executed after self-test and initialization have completed successfully.
The processor contains special purpose memory for maintaining critical configuration related parameters (e.g. Primary Boot, Alternate Boot, and Console Paths). Two forms of memory are supported: Stable Storage and Non-Volatile Memory (NVM).
Typically, when control is transferred to isl, an autoboot sequence takes place. An autoboot console device. Acceptable input is any isl command name or the name of any utility available on the system. If a non-fatal error occurs or the executed utility returns, isl again prompts for input.
Commands
There are several commands available in isl. The following is a list of them with a short descrip-tion. Parameters may be entered on the command line following the command name. They must be separated by spaces. lsi prompts for any necessary parameters that are not entered on the
Help -- Lists commands and available utilities Lists available utilities
Enables or disables the autoboot sequence Parameter -- on or off
Enables or disables the autosearch sequence Parameter -- on or off
Modify the Primary Boot Path
Parameter -- Primary Boot Path in decimal Modify the Alternate Boot Path
Parameter -- Alternate Boot Path in decimal Modify the Console Path
Parameter -- Console Path in decimal Lists contents of the auto execute file
Displays the Primary Boot, Alternate Boot, and Console Paths Displays the contents of one word of NVM in hexadecimal
Parameter -- NVM address in decimal or standard hexadecimal notation Displays the contents of one word of Stable Storage in hexadecimal
Parameter -- Stable Storage address in decimal or standard hexadecimal notation
Hewlett-Packard Company - 1 - October 1986
ISL(lM) ISL(lM) Series 800 Only
DIAGNOSTICS
lsI displays diagnostic information through error messages written on the console and display codes on the hexadecimal LED display.
For the display codes, CEOx are informative only. CElx and CE2x indicate errors, some of
Fatal errors cause the system to halt. The problem must be corrected and the system RESET to recover.
Cannot find an auto execute file. A utoboot aborted.
No console found, isl can only autoboot.
Directory of utilities is too big, isl reads only 2K bytes.
Autoexecute file is inconsistent. Autoboot aborted.
Utility file header inconsistent: SOM values invalid.
Autoexecute file input string exceeds 2048 characters. Autoboot aborted.
lsI command or utility name exceeds 10 characters.
lsI has transferred control to the utility.
Internal inconsistency: Volume label- FATAL.
Internal inconsistency: Directory - FATAL.
Error reading autoexecute file.
Error reading from console - FATAL.
Error writing to console - FATAL.
Not an isl command or utility.
Utility file header inconsistent: Invalid System ID.
Error reading utility file header.
Utility file header inconsistent: Bad magic number.
Utility would overlay isl in memory.
Utility requires more memory than is configured.
Error reading utility into memory.
Incorrect checksum: Reading utility into memory.
Console needed - FATAL.
Internal inconsistency: Boot device class - FATAL.
Destination memory address of utility is invalid.
Utility file header inconsistent: pdc_cache entry.
Hewlett-Packard Company - 2 - October 1986
ISL(lM)
CE23 CE24 CE25 CE26 CE27 SEE ALSO
Series 800 Only
Internal inconsistency: iodc_entTy-init -FATAL.
Internal inconsistency: iodc_entTy-init -console - FATAL.
Internal inconsistency: iodc_entTy-init -boot device - FATAL.
Utility file header inconsistent: Bad aux...id.
Bad utility file type.
boot(lM), hpuxboot(lM), pdc(lM).
ISL(lM)
Hewlett-Packard Company - 3 - Version B.l, October 1986
KILL ALL ( 1M) HP-UX KILLALL (1M)
NAME
killall - kill all active processes SYNOPSIS
/ ete /killall [ signal J DESCRIPTION
FILES
Killall is a procedure used by jete/shutdown to kill all active processes not directly related to the shutdown procedure.
Kil/all is chiefly used to terminate all processes with open files so that the mounted file systems will be unbusied and can be unmounted. Killall sends the specified signal to all user processes in the system, with the following exceptions:
the init process;
all processes (including background processes) associated with the terminal from which kil/all was invoked;
any ps -ef process, if owned by root;
any sed -e process, if owned by root;
any shutdown process;
any kil/all process;
any /etc/rc process.
Killall obtains its process information from ps(l), and thus may not be able to perfectly identify which processes to signal.
If no signal is specified, a default of 9 (kill) is used.
Killall is invoked automatically by shutdown(lM). The use of shutdown is recommended over using kil/all by itself.
/etc/shutdown SEE ALSO
fuser(lM), kill(l), ps(l), shutdown(lM), signal(2).
Hewlett-Packard Company - 1 - Version B.l, October 1986
LINK(lM) HP-UX
NAME
link, unlink - exercise link and unlink system calls SYNOPSIS
fete/link file1 file2 fete/unlink file DESCRIPTION
LINK(lM)
Link and unlink perform their respective system calls on their arguments, abandoning most error checking. These commands may only be executed by the super-user.
RETURNS
o -
successful link.1 - input syntax error.
2 -link call failed (unlink will never report failure).
SEE ALSO
rm(l), link(2), unlink(2).
INTERNATIONAL SUPPORT