|
|
|
strmsgsz(5) -- maximum size of streams message data (bytes)
|
|
This tunable limits the number of bytes of message data that can be inserted by putmsg() or write() in the data portion of any streams message on the system. If the tunable is set to zero, there is no limit on how many bytes can be placed in the data segment of the message. putmsg() returns [ERANGE] if the buffer being sent is larger than the current value of STRMSGSZ; write() segments the data in... |
|
STRMSGSZ(5) -- maximum size of streams message data (bytes)
|
|
This tunable limits the number of bytes of message data that can be inserted by putmsg() or write() in the data portion of any streams message on the system. If the tunable is set to zero, there is no limit on how many bytes can be placed in the data segment of the message. putmsg() returns [ERANGE] if the buffer being sent is larger than the current value of STRMSGSZ; write() segments the data in... |
|
|
st_ats_enabled(5) -- determines whether to reserve a tape device on open
|
|
This tunable notifies the stape driver whether it needs to reserve a tape device on open and subsequently release it on close. With this tunable on, the stape driver won't necessarily attempt to reserve any tape device on open. The driver has a few tape devices flagged as suitable devices for this functionality. This list includes the DLT 8000, DLT 7000, STK 9840, HP Ultrium, and STK SD-3 drives.... |
|
st_fail_overruns(5) -- determines whether variable block mode read requests smaller than the physical record size will fail
|
|
This tunable determines whether variable block mode read requests through the stape driver, that are smaller than the physical record size, will fail with the error [EFBIG]. For example, if a variable block mode read request of 32K was sent to a tape device with media of record size 64K, the entire record's data would not be returned to the host. If the tunable was set to non-zero (on), the read ... |
|
st_large_recs(5) -- determines maximum logical record size allowed through the stape driver
|
|
This tunable governs the maximum size of records allowed for tape device I/O through the stape driver. Larger records can be sent, but the I/O subsystem will split the request into multiple requests with a maximum record size determined by this tunable. For instance, if a read of 512K were sent to a tape device on a system with MAXPHYS at 256K, two scenarios would exist. With st_large_recs set to ... |
|
st_san_safe(5) -- determines whether access to stape device special files
|
|
This tunable notifies the stape driver whether it should allow access to device special files without the no-rewind-on-close option. With this tunable on, the stape driver will fail any open on a stape device special file without the no-rewind-on-close option (i.e., /dev/rmt/1m or /dev/rmt/1mb) with a status of [EINVAL]. The st_san_safe tunable allows the safe sharing of tape devices in SAN tape b... |
|
suffix(5) -- file-name suffix conventions
|
|
The following list summarizes file name suffix conventions that can be found in an HP-UX system. It is a partial compilation of possibly useful knowledge, suggestions, and explanations, rather than a specification of standards. Suffixes are often used in preference to prefixes because they enable related files to group together alphabetically in a directory listing. Note that some programs require... |
|
swapmem_on(5) -- allow physical memory size to exceed the available swap space
|
|
In previous versions of HP-UX, system configuration required sufficient physical swap space for the maximum possible number of processes on the system. This is because HP-UX reserves swap space for a process when it is created, to ensure that a running process never needs to be killed due to insufficient swap. This was difficult, however, for systems needing gigabytes of swap space with gigabytes ... |
|
swchunk(5) -- swap chunk size in 1 KB blocks
|
|
Swap space in the kernel is managed using 'chunks' of physical device space. These chunks contain one or more (usually more) pages of memory, but provide another layer of indexing (similar to inodes in file systems) to keep the global swap table relatively small, as opposed to a large table indexed by swap page. swchunk controls the size in physical disk blocks (which are defined as 1 KB) for ea... |
|
sysv_hash_locks(5) -- System V IPC hashed spinlock pool size
|
|
The sysv_hash_locks tunable specifies the size of the hashed spinlock (kernel data structures used for synchronization) pool (number of available spinlocks). The System V IPC semaphore functions acquire hashed spinlocks based on the semaphore ID. The spinlocks are hashed to avoid the memory user needed for semmni spinlocks but to also avoid the contention of having just one spinlock. For more info... |
|
tcphashsz(5) -- determines the size of the networking hash tables
|
|
This variable is used to set the size of the networking hash tables. A system that is going to have a large number of connections on it all of the time may see some benefit of increasing this value. This tunable needs to be a power of two. If it is not specified as a power of two, then it is rounded down to the nearest power of two. Who Is Expected to Change This Tunable? Anyone. |
|
term(5) -- terminal capabilities
|
|
The following data type is defined through typedef: TERMINAL An opaque representation of the capabilities for a single terminal from the terminfo database. The header provides a declaration for the following object: cur_term . It represents the current terminal record from the terminfo database that the application has selected by calling set_curterm(). The header contains the va... |
|
thread_safety(5) -- list of libc, libpthread and libgen interfaces which
|
|
Refer to this man page when writing thread-safe applications using libc, libpthread and libgen interfaces. This man page gives the list of libc, libpthread and libgen interfaces which are: Not thread-safe, Cancellation Points, Cancel Safe, Async Signal Safe, and Async Cancel Safe. |
|
timeslice(5) -- scheduling interval in clock ticks per second
|
|
The timeslice tunable defines the scheduling time interval that a thread may execute on a processor before the kernel scheduler will context switch out the thread for other same priority threads to run. When a thread starts executing on a processor, the thread is set up to run for the number of ticks in the timeslice tunable. On every clock interrupt that a thread is found executing, the time quan... |
|
timezone(5) -- difference between Universal (Greenwich mean) time and Local time
|
|
The timezone tunable is the difference between Greenwich mean time (Universal Time) and local time, expressed as minutes west of Greenwich, England. The dst tunable indicates whether the timezone tunable is to be interpreted as a standard or daylight savings time value. These tunables provide a way to convert between Grenwich Mean Time (or Universal Time) and local time. Although timezone is a tun... |
