Unix Administration

Steps to Follow: How To Verify Remote System Controller(RSC) is Configured and Current 1.Check to see if the RSC software is already installed. # /usr/bin/pkginfo | grep SUNWrsc 2.If the software is installed the command should output the package name and info.   The version of the package installed in Solaris should match the version of firmware installed on the card.   `rscadm version` in Solaris will display the firmware version. 3.If the software is not installed the packages can be found on the supplemental CD that came with the Solaris Operating Environment. If you do not have the CD the software can be downloaded from MOS: RSC 2.2.2 is supported with Solaris 10, but you need to get this from a supplemental CD (for Solaris 9, since there is no supplemental CD for S10). The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are...

Symptoms Setting LD_LIBRARY_PATH or compiling/linking with -L can cause programs to be unable to find shared libraries. For example, LD_LIBRARY_PATH was set to /usr/openwin/lib when this error appeared: "ld.so.1: myprogram : fatal : libXt.so.4 : cannot open file : error no 2" Cause Different LD_LIBRARY_PATH settings can have a variety of effects when linking, compiling and finding shared libraries for a given application. Solution The following tips are recommended for overcoming the above problem: 1. When linking (using a compiler, ld, or ild), use the -R option to specify the path used by ld.so.1 (the runtime linker) to search for shared libraries at runtime. This is preferable to using LD_RUN_PATH or LD_LIBRARY_PATH. Note: The linker behavior changed from SunOS 4.x to Solaris. In SunOS 4.x, -L specified the search paths at both link (build) time and run time. However, in Solaris (SunOS 5.x), -L specifies link time paths and -R specifies run time paths. The behavior of LD_...

Symptoms # more  ./xyz ld.so.1: more: fatal: libcurses.so.1: open failed: No such file or directory. Cause This can be due to several reasons:  - deleting the library by error  - corruption of file systems  - missing library package(s)  - wrong LD_LIBRARY_PATH variable  - wrong entry in configfiles /var/ld/ld.config or /var/ld/64/ld.config  - wrong version of 3rd party package Checks: ------------------------------------------------------------------------------- Capture the given error message of a  program       i.e.  ld.so.1: more: fatal: libcurses.so.1: open failed: No such file or directory. --------------------------------------------------------------------------------  List which libraries are required by a program using  ldd(1) or pvs(1)  or dump(1) % /usr/bin/ldd  /usr/bin/more         libcurses.so.1 =>        /lib/...

Beginning with Solaris 8 kernel patch 108528-18 for SPARC(R) and 108529-18 for x86, a sanity check has been added in ufs module to check for inode inconsistency. Due to improper fsck usage these messages get emitted into system console and /var/adm/messages file: Patch 108528-18 Patch 108529-18 Without logging: "NOTICE: : unexpected free inode , run fsck(1M)" With logging enabled: "NOTICE: : unexpected free inode , run fsck(1M) -o f" There are additional sanity checks which result in seeing the following messages: Without logging: "NOTICE: : unexpected allocated inode , run fsck(1M)" With logging enabled: "NOTICE: : unexpected allocated inode , run fsck(1M) -o f" Troubleshooting Steps If the systems display the unexpected inode messages: * Check /var/adm/messages for multiple entries for the same inode number * Check to see if there are any inode entries under /lost+found directory. If the inode entry matches with t...