Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!uwvax!oddjob!gargoyle!ihnp4!occrsh!occrsh.ATT.COM!rjd From: rjd@occrsh.ATT.COM Newsgroups: comp.unix.wizards Subject: Re: login prompt not staying set Message-ID: <142700007@occrsh.ATT.COM> Date: Fri, 4-Dec-87 22:21:00 EST Article-I.D.: occrsh.142700007 Posted: Fri Dec 4 22:21:00 1987 Date-Received: Thu, 10-Dec-87 21:38:39 EST References: <142700001@occrsh.ATT.COM> Lines: 21 Nf-ID: #R:occrsh.ATT.COM:142700001:occrsh.ATT.COM:142700007:000:903 Nf-From: occrsh.ATT.COM!rjd Dec 4 21:21:00 1987 > > (Lots of stuff concerning the getty - login sequence) > > Believe me, Im a novice at this. But it occurred to me . . . > > Does it make sense for login, after an invalid password, to exec getty > rather than issue its own login: prompt? This would eliminate the two > login: prompts (surely a goodness), but would it tie login too closely > to getty? > > I dont know, just ruminating. Sounds good to me, especially for the guy who asked the original question... To actually implement would be slightly harder, as getty expects the gettydefs line to get the parameters to set the port to, which the login program does not know. Maybe change both login and getty to check another file for the login prompt and keep the sequence the same, or have just login only prompt for it (which I see problems with), or........ EDUCATE the users to not be bothered by it......Na, thats too easy... Randy