On Thu, 19 Feb 1998, Hamish Moffatt wrote: > On Wed, Feb 18, 1998 at 01:13:52PM -0600, Jens B. Jorgensen wrote: > > Ah yes. Welcome to the magic of telnetd/login and getty/login. The first > > login: prompt is supplied by your getty/telnetd. When you type in your > > login and hit enter, the getty/telnetd execs /bin/login, passing the > > username you typed in. If you enter an incorrect login, control does not > > pass back to your getty/telnetd but instead /bin/login spits out another > > login: prompt. Pretty clever no? (No.) This is rather annoying but this way > > of "logging people in" is quite ingrained in unix. > > > > Anyway, I believe /bin/login gets the prompt from /etc/issue. Perhaps a bug > > should be filed regarding '\?' substitution. > > login doesn't seem to try to show issue again here. > The getty is mingetty.
I managed to reproduce the problem here. My /etc/login.defs showed:- #ISSUE_FILE /etc/issue and the result was:- Debian GNU/Linux 2.0 (unstable) elm tty6 elm login: allen Password: Login incorrect elm login: elm login: Debian GNU/Linux 2.0 (unstable) elm tty6 elm login: But when I change login.defs to show:- ISSUE_FILE /etc/issue the result is:- Debian GNU/Linux 2.0 (unstable) elm tty7 elm login: allem Password: Login incorrect Debian GNU/\s 2.0 (unstable) \n \l elm login: Debian GNU/Linux 2.0 (unstable) elm tty7 elm login: So it's bin/login not knowing about the escape codes that is the problem. I guess the answer is to point ISSUE_FILE to a different file with no escapes. Or just comment it out. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen <[EMAIL PROTECTED]> Perth, Western Australia voice +61 8 9316 2486 32.0125S 115.8445E vk6lj Debian Unix =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
