Solaris Crash Analysis Tool 5.2
Solaris Crash Analysis Tool (SolarisCAT) 5.2 is released. You can download it from the Sun Download Center site. From the Release Notes, there is not much difference from the SolarisCAT 5.1.
How to swap the Caps Lock and Control keys on Solaris 10
- Edit the ~/.xmodmap file.
Add the following lines to the file.remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L - Edit the ~/.dtprofile file.
Add the following lines to the file.if [ -f ~/.xmodmaprc ] ; then
/usr/openwin/bin/xmodmap ~/.xmodmaprc
fi
Solaris Crash Analysis Tool 5.1 GA
Solaris Crash Analysis Tool (Solaris CAT) 5.1 is released. You can download it from the SUN download site. Also you can read the release notes on this page.
How to check your PostgreSQL version
- Log in to your system
- Switch to 'root' or a database admin user
$ su -
- Issue the following command
# psql -V
or# psql --version
Allowed memory size of 8388608 bytes exhausted on RHEL 5
When I tried to install the Fileinfo module from the PECL site, I got the following error message.
Even though I set the memory_limit variable to 32M which is over 8M!
Here is a workaround for this issue.
Insert the following line to the /usr/share/pear/pearcmd.php file.
Then, run the pecl command again. Now you can install the module without the above error message :-)
$ pecl -v install fileinfo
(snip)
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 143 bytes) in /usr/share/pear/PEAR/PackageFile/v2.php on line 1140
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 100 bytes) in /usr/share/pear/PEAR.php on line 765
Even though I set the memory_limit variable to 32M which is over 8M!
$ php -i | grep memory_limit
memory_limit => 32M => 32M
Here is a workaround for this issue.
Insert the following line to the /usr/share/pear/pearcmd.php file.
@ini_set('memory_limit', '32M');
Then, run the pecl command again. Now you can install the module without the above error message :-)
Red Hat Enterprise Linux Version Comparison
The lam-libs package update failed on RHEL4
When I used the up2date command to upgrade my RHEL system from RHEL4.6 to RHEL4.7, I got the following error message.
The messages said "scriptlet failed", so I checked the scriptlet of the lam-libs package with the rpm command
As you can see the above result, the alternatives command was ran at the %preun section and it failed because the mpilibs32 entry was not found under the /etc/alternatives directory. That entry was removed by the lam-libs (7.1.2-15) package when the package was updated. Therefore if you want to update the lam-libs package, you should try the following:
Remove the old lam-libs package without executing the pre-/post-uninstall scripts, and update the package.
Or
Create the mpilibs32 entry with the alternatives command, remove the old lam-lib package, and update the package.
error: %preun(lam-libs-7.1.2-8.i386) scriptlet failed, exit status 2
There was a fatal RPM install error. The message was:
Failed running rpm transaction
The messages said "scriptlet failed", so I checked the scriptlet of the lam-libs package with the rpm command
# rpm -q --scripts lam-libs
postinstall scriptlet (using /bin/sh):
alternatives --install /etc/ld.so.conf.d/mpi32.conf \
mpilibs32 /usr/lib/lam/lam.ld.conf 5
/sbin/ldconfig
preuninstall scriptlet (using /bin/sh):
alternatives --remove mpilibs32 /usr/lib/lam/lam.ld.conf
postuninstall program: /sbin/ldconfig
As you can see the above result, the alternatives command was ran at the %preun section and it failed because the mpilibs32 entry was not found under the /etc/alternatives directory. That entry was removed by the lam-libs (7.1.2-15) package when the package was updated. Therefore if you want to update the lam-libs package, you should try the following:
Remove the old lam-libs package without executing the pre-/post-uninstall scripts, and update the package.
# rpm -e --noscript lam-libs-7.1.2-8
# /sbin/ldconfig
# rpm -Uvh lam-libs-7.1.2-15.el4.i386.rpm
Or
Create the mpilibs32 entry with the alternatives command, remove the old lam-lib package, and update the package.
# alternatives --install /etc/ld.so.conf.d/mpi32.conf mpilibs32 /usr/lib/lam/lam.ld.conf 5
# rpm -e lam-libs-7.1.2-8
# rpm -Uvh lam-libs-7.1.2-15.el4.i386.rpm
Subscribe to:
Posts (Atom)
Good Bye, Folks!
As you may have heard, Fujitsu has completely discontinued Data Center Products and Solutions business in North America on April 1st, 2021. ...
-
For some reason, the iRMC admin user password is lost, and you need to recover it to access the iRMC on your PRIMERGY server. The official w...
-
As you probably know, iRMC S5 supports auto discovery. Fujitsu has management software like Infrastructure Manager (ISM) that supports iRMC...
-
There is a HTTP interface in iRMC for system BIOS and iRMC firmware updates. That means you can send firmware images to iRMC remotely to fla...