|
|
|
termios(7) -- general terminal interface
|
|
All HP-UX asynchronous communications ports use the same general interface, regardless of what hardware is involved. Network connections such as rlogin (see rlogin(1) use the pseudo-terminal interface (see pty(7). This discussion centers around the common features of this interface. |
|
termiox(7) -- extended general terminal interface
|
|
The extended general terminal interface supplements the termio(7) general terminal interface by adding support for asynchronous hardware flow control and local implementations of additional asynchronous features. Some systems may not support all of these capabilities because of hardware or software limitations. Other systems may not permit certain functions to be disabled. In such cases, the appro... |
|
|
timod(7) -- STREAMS module for converting ioctl() calls into Transport Interface messages
|
|
The timod module is a STREAMS module that converts ioctl() calls from a transport user supporting the Transport Interface (TI) into messages that a transport protocol provider supporting TI can consume. This allows the user to initiate certain TI functions as atomic operations. This release of HP-UX no longer automatically pushes timod whenever a t_open(3) is performed. The TLI and XTI libraries h... |
|
tirdwr(7) -- STREAMS module for reads and writes by Transport Interface users
|
|
The tirdwr module is a STREAMS module that provides a transport user supporting the Transport Interface (TI) with an alternate interface to a transport protocol provider supporting TI. This alternate interface allows the transport user to communicate with the transport protocol provider using the read() and write() functions. It can also continue to use the putmsg() and getmsg() functions, but the... |
|
tty(7) -- controlling terminal interface
|
|
The file /dev/tty is, in each process, a synonym for the control terminal associated with the process group of that process, if any. It is useful for programs or shell sequences that need to be sure of writing messages on the terminal no matter how output has been redirected. It can also be used for programs that demand the name of a file for output, when typed output is desired and it is tiresome... |
|
urandom(7) -- strong random number generator
|
|
The character special files /dev/random and /dev/urandom provide an interface to the kernel-resident random number generator, rng. A read() from /dev/random is potentially blocking, as compared to a read from /dev/urandom which is always nonblocking. Data from /dev/urandom can potentially have lower entropy than data from /dev/random. The rng module is a dynamically loadable kernel module (DLKM). ... |
|
VLAN(7) -- virtual LANs (VLANs)
|
|
VLANs are logical, or "virtual," network segments that can span multiple physical network segments. A primary benefit of VLANs is that they can isolate broadcast and multicast traffic by determining which destinations should receive that traffic, thereby making better use of switch and end-station resources. The commands described here are for interactive administration of HPUX virtual LANs (VLA... |
|
vlan(7) -- virtual LANs (VLANs)
|
|
VLANs are logical, or "virtual," network segments that can span multiple physical network segments. A primary benefit of VLANs is that they can isolate broadcast and multicast traffic by determining which destinations should receive that traffic, thereby making better use of switch and end-station resources. The commands described here are for interactive administration of HPUX virtual LANs (VLA... |
|
vxconfig(7) -- VERITAS Volume Manager configuration device
|
|
The vxconfig device is the interface through which all changes to the volume driver state are performed in VERITAS Volume Mananger (VxVM). This device can only be opened by one process at a time. The initial volume configuration is downloaded into the kernel through this device. The vxconfigd process updates the configuration through this device. The vxconfigd process was designed to be the sole a... |
|
vxdmp(7) -- VERITAS Volume Manager multipathing disk devices
|
|
Multipathed disk devices in VERITAS Volume Manager (VxVM) represent virtual devices with one or more physical access paths to a physical disk. The Multipathing feature provides disk access reliability by dynamically switching to another physical path if there is a path failure. Every disk that is visible to VxVM is represented by a multipath device node in the /dev/vx/dmp and /dev/vx/rdmp director... |
|
vxfsio(7) -- VxFS file system control functions
|
|
The vxfs ioctl(2) enhancements provide for extended control over open files. The argument fildes is an open file descriptor. The data type and value of arg are specific to the type of command specified by cmd. Unless specified, arg is treated as an int type. The symbolic names for commands and file status flags are defined by the sys/fs/vx_ioctl.h header file. |
|
vxinfo(7) -- VERITAS Volume Manager general information device
|
|
The vxinfo device in VERITAS Volume Manager (VxVM) gathers performance statistics from the kernel for a supplied object. Statistics can be retrieved for volume, plex, subdisk, and disk media objects. Statistics can also be cleared through this interface. |
|
vxio(7) -- VERITAS Volume Manager virtual disk devices
|
|
Volume devices are the virtual disk devices in VERITAS Volume Manager (VxVM). The volume devices support a virtual disk access method with disk mirroring and disk striping. A volume is a logical entity composed of one or more plexes. A read can be satisfied from any plex, while a write is directed to all plexes. The virtual disk devices have a wide variety of behaviors, which are programmable thro... |
|
vxiod(7) -- VERITAS Volume Manager I/O daemon process control device
|
|
The vxiod device in VERITAS Volume Manager (VxVM) is used to control the number of volume I/O daemons active on the system. A process context is necessary to implement the plex consistency recovery and writeback error handling policies for multi-plex volumes, and for continuing normal I/O after a log write if the volume has logging enabled. It is also required for the plex recovery performed with ... |
|
vxtrace(7) -- VERITAS Volume Manager I/O Tracing Device
|
|
The vxtrace device implements the VERITAS Volume Manager (VxVM) I/O tracing and the error tracing. An I/O tracing interface is available that users or processes can use to get a trace of I/Os for specified sets of kernel objects. Each separate user of the I/O tracing interface can specify the set of desired trace data independent of all other users. I/O events include regular read and write operat... |
