|
|
|
pam_dce(5) -- authentication, account, and password management PAM functions for DCE
|
|
The DCE PAM modules allow integration of DCE into the system entry services (such as login, telnet, rlogin, ftp) through the pam.conf(4) file. The DCE service module for PAM consists of the following three modules: the authentication module, the account management module, and the password management module. All three modules are supported through the same loadable library, /usr/lib/security/libpam... |
|
pam_hpsec(5) -- extended authentication, account, password, and session
|
|
The pam_hpsec service module implements extensions specific to HP-UX for authentication, account management, password management, and session management. The use of pam_hpsec is mandatory for services like login, dtlogin, ftp, remsh/rexec and ssh. It is required that these services stack this module on the top of the stack above one or more non-optional modules such as pam_unix, pam_krb5, or pam_l... |
|
|
pam_krb5(5) -- authentication, account, session and password management modules for Kerberos 5
|
|
The KRB5 PAM modules allow integration of Kerberos authentication into the system entry services (such as login, ftp) using pam.conf(4) configuration file. The Kerberos service module for PAM consists of the following four modules: Authentication module, Account management module, Session management module and Password management module. All modules are supported through the same dynamically loada... |
|
pam_unix(5) -- authentication, account, session, and password management PAM modules for UNIX
|
|
The UNIX service module for PAM, /usr/lib/security/$ISA/libpam_unix.so.1, provides functionality for all four PAM modules: authentication, account management, session management and password management. The libpam_unix.so.1 module is a shared object that can be dynamically loaded to provide the necessary functionality upon demand. For an interpretation of the module path, please refer to the relat... |
|
pam_updbe(5) -- User policy definition service module
|
|
The user policy definition service module for PAM, /usr/lib/security/$ISA/libpam_updbe.so.1, reads options defined in the user configuration file, /etc/pam_user.conf (see pam_user.conf(4)) and uses pam_set_data (see pam_set_data(3)) to store the information in the pam handle for subsequent service modules to use. Service modules perform pam_get_data to retrieve corresponding information from the p... |
|
partition(5) -- display information about the Partition Command Line Interface
|
|
This manpage gives a listing and brief description of the commands which are used to manage a partitionable system. Command | Description ___________|___________________________________________________ cplxmodify | Modify an existing complex. | parcreate | Create a new partition. | parmodify | Modify an existing partition. | parstatus | Display partition and available resources | information for a... |
|
passwd_override(5) -- The registry database override file
|
|
The dcelocal/etc/passwd_override administrative file lets you override the password, GECOS, home directory, login shell, group membership, and principal UNIX ID information stored in the network registry database. The /etc/passwd_override administrative file lets you override the password, GECOS, home directory, login shell, group membership, and principal UNIX ID information stored in the network... |
|
pa_maxssiz(5) -- maximum size (in bytes) of the
|
|
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. PA-RISC binaries running under Itanium-based system using the PA-RISC emulator have their stack segment size (which includes both the memory stack and the RSE stack) determined by pa_maxssiz_32bit or pa_maxssiz_64bit. The emulated stack from the process perspective... |
|
pa_maxssiz_64bit(5) -- maximum size (in bytes) of the
|
|
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. PA-RISC binaries running under Itanium-based system using the PA-RISC emulator have their stack segment size (which includes both the memory stack and the RSE stack) determined by pa_maxssiz_32bit or pa_maxssiz_64bit. The emulated stack from the process perspective... |
|
pfdat_hash_locks(5) -- determines the size of the pfdat spinlock pool
|
|
Global kernel structures containing information on a running process or memory usage are frequently accessed or modified by several threads concurrently. To prevent race conditions, these structures are protected by spinlocks (kernel data used for synchronization) which allow only the spinlock structure must wait. Hashed spinlocks are used when each instance of such a data structure is to be prote... |
|
pfs_exports(5) -- directories to export to PFS clients
|
|
The /etc/pfs_exports file contains entries for directories that can be exported to PFS clients. This file is read automatically by the pfs_exportfs(1M) command. If you change this file, you must run pfs_exportfs(1M) for the changes to affect the daemon's operation. It is recommended that you place a command in rc(1M) so that pfs_exportfs(1M) is executed at boot time. The /etc/pfs_xtab file contai... |
|
pfs_fstab(5) -- static file system mounting table, mounted file systems table
|
|
The /etc/pfs_fstab file contains entries for CD-ROM file systems and disc images to mount using the pfs_mount(1M) command, which is normally invoked by rc(1M) script at boot time. This file is used by various utilities such as pfs_mount and pfs_umount. The /etc/mtab file contains entries for file systems currently mounted, and is read by programs using the routines described in getmntent(3X). umou... |
|
pfs_xtab(5) -- directories to export to PFS clients
|
|
The /etc/pfs_exports file contains entries for directories that can be exported to PFS clients. This file is read automatically by the pfs_exportfs(1M) command. If you change this file, you must run pfs_exportfs(1M) for the changes to affect the daemon's operation. It is recommended that you place a command in rc(1M) so that pfs_exportfs(1M) is executed at boot time. The /etc/pfs_xtab file contai... |
|
physical_io_buffers(5) -- total buffers for physical I/O operations
|
|
Many physical I/O operations in the kernel use a shared pool of small pieces of memory (buffers) to hold data being read or written to the I/O device. If no buffer is provided to the I/O operation routine, and no kernel buffers are available because they are already in use for other physical I/O transactions, the caller must wait for an available buffer. Under heavy I/O load with many threads atte... |
|
portal(5) -- a "window to the future" for applications
|
|
This header file is a "window to the future" for applications. It will help you to: + Write code that is portable across 32-bit and 64-bit systems, + Avoid undocumented assumptions about sizes of integral types, + Write portable code that needs to be explicit about the sizes of integral types, + Write code that is portable to a platform which has different sizes of integral types, and + Share fr... |
