Newsgroups: comp.unix.aix Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!mcover From: mcover@magnus.acs.ohio-state.edu (Mark Coverdill) Subject: Re: utmp fix? Message-ID: <1991Jun3.031118.27347@magnus.acs.ohio-state.edu> Sender: news@magnus.acs.ohio-state.edu Nntp-Posting-Host: bottom.magnus.acs.ohio-state.edu Organization: The Ohio State University References: <1991May30.011132.28981@magnus.acs.ohio-state.edu> <19352@rpp386.cactus.org> Date: Mon, 3 Jun 1991 03:11:18 GMT Lines: 35 In article <19352@rpp386.cactus.org> jfh@rpp386.cactus.org (John F Haugh II) writes: >This is a program that I use here to keep my utmp file clean. I >posted it once before and someone at IBM brushed it up and made >it look pretty. Here it is again ... >-- [ program deleted ] As a followup to my original posting about the utmp file, I called Defect Support at IBM about this problem. They said that they indeed knew about the problem and the fix didn't make it into 3005 but would be glad to send me 2006 (I guess this is the title for intermediate fixes between major fixes??). I applied 2006 and now everything works like a charm! They even sent the fix by overnight mail so all told the problem was solved in less than 48 hours, even faster than the net on this particular occasion (score one for IBM :-)). BTW, 2006 was more than just a fix to the utmp file, much more. It was late Friday afternoon so I didn't get a chance to scan the change list but many of the major lpp's such as bos.obj, etc. were brought up to 003.0006.0012 (I think?) not to mention it took close to an hour to upgrade (much to my surprise!). Anyway, I'm happy, my users are happy and the computer is happy, so those of you with the same problem can look for 2006 or possibly 3007 in the not so distant future :-) A big thanks to all those who responded... Mark BTW, the system is an RS 6000/320 running AIX v3.1.5/2006. -- Mark Coverdill The Ohio State University Internet: mcover@magnus.acs.ohio-state.edu Columbus, Ohio