Training AIX Best Practice : contoh kasus who -u tidak berfungsi

Apa kabar CommUNIXy,

Sangat lama juga ya nggak update blog ini. Mudah-mudahan semua pengunjung setiap blog ini dalam kondisi sehat wal afiat. Oh ya, minggu lalu NgoprekUNIX baru saja menuntaskan sesi training "AIX Best Practice" yang didesain khusus untuk praktisi baik engineer maupun SysAdmin. Sekedar bocoran, buat yang penasaran berikut adalah kisi-kisi materinya :


Session 1
Unit 1 - Introduction to be a professional engineer

Session 2
Unit 2 – Introduction to Pseries  System

Session 3
Unit 2 - System Management Tools and Documentation
Unit 3 - System Startup and Shutdown
Unit 4 - Devices

Session 4
Unit 5 - System Storage Overview

Session 5
Unit 6 - Working With the Logical Volume Manager
 
Session 6
Unit 7 - Working with File Systems
Unit 8 - Managing File Systems

Session 7
Unit 9 - Paging Space
Unit 10 - AIX V5.3 Installation (optional)
Unit 11 - AIX Software Installation and Maintenance

Session 8
Unit 12 - Backup and Restore

Session 9
Unit 13 - Security and User Administration

Session 10
Unit 14 - Scheduling
Unit 15 - Printers and Queues
Unit 16 - Networking Overview

Session 11
Unit 17 - VI Editor
Unit 18 – Problem Determination


Nah, buat yang mau memperdalam ilmu kedigdayaan AIX, silakan deh kopi darat ke Paradigma Training Center (www.paradigma.co.id - 021 3911712) untuk reservasi kelas.

Oh ya, sesuai dengan komitmen NgoprekUNIX dalam berbagi ilmu dan tips-tips tokcer, kali ini akan disuguhkan contoh kasus who -u tidak berfungsi. 
Berikut adalah output error yang terjadi :
$ who -u
whydi_so   pts/5        Feb 21 11:03  0:34   6429       (10.192.23.160)
whydi_so   pts/6        Feb 21 11:38   .     7329       (10.192.23.160)
who: Error --- entry has ut_type of 29728
 when maximum is 10
who: Error --- entry has ut_type of 8302
 when maximum is 10
who: Error --- entry has ut_type of 8300
 when maximum is 10
who: Error --- entry has ut_type of 26469
 when maximum is 10
who: Error --- entry has ut_type of 28526
 when maximum is 10
who: Error --- entry has ut_type of 29295
 when maximum is 10
who: Error --- entry has ut_type of 8297
 when maximum is 10
who: Error --- entry has ut_type of 28271
 when maximum is 10
who: Error --- entry has ut_type of 27759
 when maximum is 10
who: Error --- entry has ut_type of 25956
 when maximum is 10
who: Error --- entry has ut_type of 28206
 when maximum is 10
who: Error --- entry has ut_type of 28527
 when maximum is 10
who: Error --- entry has ut_type of 26995
 when maximum is 10
who: Error --- entry has ut_type of 28532
 when maximum is 10
who: Error --- entry has ut_type of 28519
 when maximum is 10
who: Error --- entry has ut_type of 25632
 when maximum is 10
who: Error --- entry has ut_type of 11786
 when maximum is 10
who: Error --- entry has ut_type of 28532
 when maximum is 10
who: Error --- entry has ut_type of 29472
 when maximum is 10
who: Error --- entry has ut_type of 29728
 when maximum is 10
who: Error --- entry has ut_type of 26471
 when maximum is 10
who: Error --- entry has ut_type of 8303
 when maximum is 10
who: Error --- entry has ut_type of 2674
 when maximum is 10
who: Error --- entry has ut_type of 29728
 when maximum is 10
who: Error --- entry has ut_type of 8302
 when maximum is 10
who: Error --- entry has ut_type of 8300
 when maximum is 10
who: Error --- entry has ut_type of 26469
 when maximum is 10
who: Error --- entry has ut_type of 28526
 when maximum is 10
who: Error --- entry has ut_type of 29295
 when maximum is 10
who: Error --- entry has ut_type of 8297
 when maximum is 10
who: Error --- entry has ut_type of 28271
 when maximum is 10
who: Error --- entry has ut_type of 27759
 when maximum is 10
Nah lho, bagaimana tuh solusinya? Padahal koman "who" dengan flag lain aman dan terkendali euy. Eit, pake user root juga tetap sama neh errornya. So, jangan kepikiran ini ada isu di previlege user ya seperti SETUID.
$ w
 11:38am  up 84 day(s), 16:28,  2 users,  load average: 0.02, 0.02, 0.02
User     tty           login@  idle   JCPU   PCPU  what
whydi_so pts/5        11:03am    34                -sh
whydi_so pts/6        11:38am                      w
root@ksipcmdev # who am i
whydi_so   pts/6        Feb 21 11:38    (10.192.23.160)
Eng..ing...eng...
Solusinya ternyata semudah mengedipkan mata hehehe...
Yaitu, kosongkan file /var/adm/utmpx.
Selamat mencoba ya. Semoga bermanfaat.
Salam NgoprekUNIX