|
|
|
sis(5) -- secure internet services with Kerberos authentication and authorization
|
|
Secure Internet Services (SIS) provides network authentication when used in conjunction with HP DCE security services, the HP Praesidium/Security Server, or other software products that provide a Kerberos V5 Network Authentication Services environment. The network authentication ensures that a local and remote host will be mutually identified to each other in a secure and trusted manner and that t... |
|
stat(5) -- data returned by the stat() function
|
|
The header defines the structure of the data returned by the functions fstat(), lstat(), and stat(). The structure stat contains at least the following members: dev_t st_dev ID of device containing file ino_t st_ino file serial number mode_t st_mode mode of file (see below) nlink_t st_nlink number of links to the file uid_t st_uid user ID of file gid_t st_gid group ID of file dev_t st... |
|
|
stdarg(5) -- macros for handling variable argument lists
|
|
The header contains a set of macros that can be used to write portable procedures that accept variable argument lists. Routines that have variable argument lists (such as printf()) but do not use stdarg are inherently nonportable, because different machines use different argument-passing conventions. va_list is a type defined for the variable used to traverse the list. va_start is calle... |
|
stdsyms(5) -- description of "named defines" and other specifications for
|
|
stdsyms is a description of "named defines" and other specifications that must be set by the application to obtain the appropriate name space from the HP-UX header files. HP-UX header files are organized in a manner that allows for only a subset of the symbols available in that header file to be visible to an application that conforms to a specific standard. The ANSI-C, POSIX.1, POSIX.2, and XPG... |
|
strctlsz(5) -- maximum size of streams message control (bytes)
|
|
STRCTLSZ limits the maximum number of bytes of control data that can be inserted by putmsg() in the control 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 control segment of the message. putmsg() returns [ERANGE] if the buffer being sent is larger than the current value of STRCTLSZ. Who Is Expected to Change Thi... |
|
STRCTLSZ(5) -- maximum size of streams message control (bytes)
|
|
STRCTLSZ limits the maximum number of bytes of control data that can be inserted by putmsg() in the control 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 control segment of the message. putmsg() returns [ERANGE] if the buffer being sent is larger than the current value of STRCTLSZ. Who Is Expected to Change Thi... |
|
streampipes(5) -- force all pipes to be STREAMS-based
|
|
This tunable determines the type of pipe that is created by the pipe() system call. If set to the default value of zero, all pipes created by pipe() are normal HP-UX file-system pipes. If the value is nonzero, pipe() creates STREAMS-based pipes, and STREAMS modules can be pushed onto the resulting stream. If this tunable is set to a non-zero value, the pipemod and pipedev module and driver must be... |
|
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 ... |
