Useful AIX Tips

1. Changing Core File path
The syscorepath utility, provided with AIX v5.2 or highter, can be used to specify a single system-wide directory where all core files of any processes will be saved. The syntax for this command is:

syscorepath -p alternate_directory

The syscorepath command enables a system administrator to set up a single
system-wide directory in which to dump core files from any processes. This can
ease administrative tasks in managing file-system space and provides a single,
known directory in which to find core files. By default, the core file is
created in the working directory of the process being coredumped.

The directory should have read and write privileges for all users on the system.
If a user does not have permission to write in the directory, a core file will
not be created. Core files will be given unique names based on the process ID
and time, so a core file will be named core.pid.MMddhhmmss, where pid is the
process ID, MM is month, dd is the day of the month, hh is the hour in 24-hour
format, mm is minutes, and ss is seconds.

2. To check the contents of a bff package
installp -pa -d$PWD/PkgName all

3. To List installed softwares
/usr/bin/lslpp

4. TO Check LPAR status:
lparstat

To Check SMT status
smtctl

5. How to recover libc.a on a AIX?
I deleted libc.a by accident --- how do I recover? From: Ed Ravin

You can recover from this without rebooting or reinstalling, if you
have another copy of libc.a available that is also named "libc.a". If
you moved libc.a to a different directory, you're in luck -- do the
following:

export LIBPATH=/other/directory


And your future commands will work. But if you renamed libc.a, this
won't do it. If you have an NFS mounted directory somewhere, you can
put libc.a on the that host, and point LIBPATH to that directory as
shown above.

Failing that, turn off your machine, reboot off floppies or other
media, and get a root shell. I don't think you should do "getrootfs"
as you usually do when accessing the root vg this way -- AIX may start
looking for libc.a on the disk, and you'll just run into the same
problem. So do an importvg, varyonvg, and then mount /usr somewhere,
then manually move libc.a back or copy in a new one from floppy.

Comments

Popular posts from this blog

Graylog - an easy solution for log management

Comparing C and Go Lang - My first impression

Nokia mobile phone - some Tips