Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!mcnc!rti!xyzzy!meissner From: meissner@xyzzy.UUCP (Michael Meissner) Newsgroups: comp.unix.wizards Subject: Re: login prompt not staying set Message-ID: <427@xyzzy.UUCP> Date: Sun, 6-Dec-87 00:43:48 EST Article-I.D.: xyzzy.427 Posted: Sun Dec 6 00:43:48 1987 Date-Received: Thu, 10-Dec-87 23:52:31 EST References: <142700001@occrsh.ATT.COM> <2932@ihlpf.ATT.COM> <623@umbc3.UMD.EDU> Reply-To: meissner@xyzzy.UUCP (Michael Meissner) Organization: Data General (Languages @ Research Triangle Park, NC.) Lines: 15 In article <623@umbc3.UMD.EDU> dipto@umbc3.UMD.EDU (Dipto Chakravarty) writes: (various correct information about the login sequence omited) > So, remember that it is "getty" which asks for ``login:'' and not the prog > login itself; that's the reason why a passwd can't be typed in before being > prompted for it on the Unix. That is not the whole story. If it was just limited to getty exec'ing to login, everything would be hunky dory. The problem is login calls the getpass function, which under BSD does a TIOCSETP ioctl, and under System V does a TCSETAF ioctl. Both of these ioctl's specify that the system is to wait until the terminal control buffers are empty before applying the ioctl. Also, in grepping the source, I noticed the 4.3 login.c also does an additional TIOCSETP on it's own. -- Michael Meissner, Data General. Uucp: ...!mcnc!rti!xyzzy!meissner Arpa/Csnet: meissner@dg-rtp.DG.COM