The best way to fix this problem is to fix the programs which are
causing the behavior in the first place. The short answer is to call
software support and ask for the “UTMPFIX” collection of PTFs.
Virtually all of these problems should be fixed in the 3251 PMP and
the only one I’ve been able to prove is still broken is using ALT-F4
to close an aixterm.
This applies if you are running an X11R5 xterm on 3.2.
Add this to the top of X11R5 mit/clients/xterm/main.c:
#define WTMP_FILENAME “/var/adm/wtmp”
And your utmp problems should go away. If you want xterminal sessions
to go into the wtmp file you need to define -DWTMP in the Imakefile and
be sure the WTMP_FILENAME is set to the right place.
Section 8.02 contains a small C program that you can use until the
PTFs arrive. The program must be run as root and will periodically
clean up old entries.
Use smitty, the standard curses version or add this line to your .kshrc file:
alias smit=”smit -C”
Many of the messages from the Unix commands are available in different languages. This is controlled by the LANG environment variable, the default being En_US meaning English in the US. All the default messages have a message number associated with them, e.g.:
$ cat no-such-file
cat: 0652-050 Cannot open no-such-file.
If you prefer the terser Unix-looking error message, set your environment variable LC_MESSAGES to C, and you will get:
$ cat no-such-file
cat: Cannot open no-such-file.
By default LC_MESSAGES is the same as your environment LANG. Setting LANG does also work, but should be avoided since it changes app-defaults lookup etc. See locale(): LC_ALL
From: Bjorn P. Brox <firstname.lastname@example.org>
AIX stores most of the system management information in /etc/objrepos, /usr/lib/objrepos, and /usr/share/lib/objrepos. Files (also referred to as system object classes) in these directories are adminstered by the Object Database Manager, ODM, which is a set of library routines and programs providing basic object oriented database facilities. Under most circumstances, only SMIT or the commands SMIT call (see 1.100) should be used to change the contents of the system object classes. A harmless way to look at the object database is to use odmget <Class> where <Class> is one of the files in /etc/objrepos. Experienced users can use the ODM editor, odme, to navigate the database in detail. Modifying the database should only be attempted if you know exactly what you are doing.