Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

libcadmin(1m) [hpux man page]

libcadmin(1M)															     libcadmin(1M)

NAME
libcadmin - libc administration command SYNOPSIS
/usr/sbin/libcadmin DESCRIPTION
The command is used to perform administrative functions for Currently the only function that the command performs is to replace the shared 32-bit PA-RISC2.0 library in with the shared 32-bit PA-RISC1.1 version of that library. There are no required arguments or options used with this command. The archive library and the symbolic link are unaffected by the com- mand. During the system installation process, the shared 32-bit PA-RISC1.1 library is copied into This library is the same as the PA-RISC2.0 library except that it was built with different compiler options. The PA-RISC2.0 library provides much higher performance than the PA- RISC1.1 library. However, if the system administrator desires to have the PA-RISC1.1 library installed instead, allows the system adminis- trator to accomplish this task. When is executed, the PA-RISC2.0 library is stored in and the PA-RISC1.1 library is copied into It is recommended that the system be re-booted after executing the command so that applications which are linked shared against will use the shared 32-bit PA-RISC1.1 version of that library. Once the command is executed, the only way to put the PA-RISC2.0 library back in place is to re-install the operating system. The command can only be executed by a user with superuser privileges. DIAGNOSTICS
Multiple executions of the command will result in an error message indicating the PA-RISC1.1 library is already installed. Executing this command on a PA-RISC1.1 machine will result in an error message indicating the PA-RISC1.1 library is already installed. RETURN VALUE
Upon successful completion, returns zero(0). Otherwise a one(1) is returned. WARNINGS
Since HP stopped shipping the PA1.1 version of beginning with HP-UX 11i Version 2, this command is currently nonfunctional. is planned for obsolescence at a future release. AUTHOR
was developed by HP. TO BE OBSOLETED libcadmin(1M)

Check Out this Related Man Page

hba.conf(4)															       hba.conf(4)

NAME
hba.conf - configuration file for the HBAAPI library The /etc/hba.conf file is used to specify the Vendor-Specific Libraries that are installed on the system. This file is used by the Common Library to load the individual VSLs when HBA_LoadLibrary(3HBAAPI) is called. If changes are made to the file while the library is in use, the library should be freed and reloaded. A version 1 VSL is compatible only with a version 1 Common Library. A version 2 VSL is compatible with both a version 1 and a version 2 Common Library. Each VSL entry is a single line of the form: "name" "library path" where: name is the description of library. The library name should be prepended with the domain of the manufacturer of the library. library path is the absolute path to the shared object library file. Example 1: Contents of /etc/hba.conf # # This file contains names and references to HBA libraries # # Format: # # <library name> <library pathname> # # The library name should be prepended with the domain of # the manufacturer or driver author. com.sun.fchba32 /usr/lib/libsun_fc.so.1 com.sun.fchba64 /usr/lib/sparcv9/libsun_fc.so.1 See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: FC-MI 1.92 (API | | |version 1) | +-----------------------------+-----------------------------+ | |Standard: FC-HBA Version 4 | | |(API version 2) | +-----------------------------+-----------------------------+ HBA_LoadLibrary(3HBAAPI), libhbaapi(3LIB), attributes(5) The HBAAPI is provided in both 32- and 64-bit versions, but only one configuration file is specified. As a result, both 32- and 64-bit VSL libraries must be specified within the same file. When using the 32-bit Common Library, the 64-bit VSLs will fail to load. When using the 64-bit Common Library, the 32-bit VSLs will fail to load. These failures are silently ignored by the Common Library during normal usage, but can result in warning messages when running client applications in a debugger. 4 Sep 2003 hba.conf(4)
Man Page