Xref: utzoo comp.sys.att:4005 unix-pc.general:1255 comp.unix.questions:8802 Checksum: 51846 Path: utzoo!utgpu!woods From: woods@gpu.utcs.toronto.edu (Greg Woods) Date: Tue, 16-Aug-88 01:08:09 EDT Message-ID: <1988Aug16.010809.16831@gpu.utcs.toronto.edu> Organization: G. A. W. Constulting Newsgroups: comp.sys.att,unix-pc.general,comp.unix.questions Subject: Re: getlogin() problem (was Re: username problem) References: <578@proxftl.UUCP> <467@icus.UUCP> Reply-To: woods@gpu.utcs.Toronto.EDU (Greg Woods) In article <467@icus.UUCP> lenny@icus.UUCP (Lenny Tropiano) writes: >In article <578@proxftl.UUCP> aaron@proxftl.UUCP (Aaron Zimmerman) writes: >|>I have a curious problem on my 3b1... >|> >... >|>$ who am i >|>aaron w4 Aug 12 08:01 >|>$ passwd >|>Changing password for LOGIN >|>Permission denied. >... > >The problem occurs not in passwd (or the /etc/passwd file), but in the >getlogin(3C) function call. This problem occurs if you use multiple >getty's on /dev/window, or you have something running on w1 when the >getty respawns for /dev/window. I've also had this problem with 386/ix, when a getty in the LOGIN state dies abnormally. A 'who -a' shows LOGIN and xyzzy both on the port, but it gives an exit status for LOGIN. I'd call this a bug (and I will bug-report it too). The problem occurs with any utility that calls getlogin(3C), including mail, etc. -- Greg Woods. UUCP: utgpu!woods, utgpu!{ontmoh, ontmoh!ixpierre}!woods VOICE: (416) 242-7572 [h] LOCATION: Toronto, Ontario, Canada