Xref: utzoo comp.windows.x:31869 comp.sys.hp:7479 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!uflorida!travis!tom From: tom@ssd.csd.harris.com (Tom Horsley) Newsgroups: comp.windows.x,comp.sys.hp Subject: Re: Corrupt utmp entry on HPs Message-ID: Date: 25 Jan 91 18:22:32 GMT References: <1991Jan24.191810@axion.bt.co.uk> Sender: news@travis.csd.harris.com Followup-To: comp.windows.x Organization: Harris Computer Systems Division Lines: 25 In-reply-to: iwarner@axion.bt.co.uk's message of 24 Jan 91 19:18:10 GMT I don't know if you have the same problem as we do at here, but we had this happen because some code in xterm was doing a strcpy rather than a strncpy when setting up the utmp entry it was going to create. Everything was working fine until we started using the name daemon, then names that used to be things like "sys1" turned into names like "sys1@blah.blah.blah.blah" and the field it was writing the remote system name in wrote across a bunch of data in subsequent fields of the utmp entry. The wonderful unix library routines then are perfectly willing to insert gibberish into the utmp file, but the other wonderful unix library routines that read utmp files are not willing to skip corrupted entries. On the other hand, the specific error you mentioned: No utmp entry.You must exec "login" from the lowest level "sh". I often find is caused by running out of ptys. -- ====================================================================== domain: tahorsley@csd.harris.com USMail: Tom Horsley uucp: ...!uunet!hcx1!tahorsley 511 Kingbird Circle Delray Beach, FL 33444 +==== Censorship is the only form of Obscenity ======================+ | (Wait, I forgot government tobacco subsidies...) | +====================================================================+