Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!sharkey!tygra!cat From: cat@tygra.ddmi.com (CAT-TALK Maint. Account) Newsgroups: comp.unix.xenix Subject: Re: problems with ungetty Message-ID: <360@tygra.ddmi.com> Date: 20 Aug 90 22:11:37 GMT References: <5476@thebes.Thalatta.COM> Reply-To: cat@tygra.UUCP (CAT-TALK Maint. Account) Organization: CAT-TALK Conferencing Network, Detroit, MI Lines: 20 In article <5476@thebes.Thalatta.COM> campbell@Thalatta.COM (Bill Campbell) writes: } }I think there may be a problem with your modem or the Stallion }drivers. getty shouldn't even be running unless CD is up on the }modem line. Would it be logical for getty to get out of the way }if it thought it was in the process of answering an incoming call? }-- WRONG! getty's are spawned by init when (1) the system is started and (2) When someone logs off (ie: login process terminates) or when the current getty on the line dies. CD is only up when someone has dialed in. Getty is also present when no one is connected. It simply waits for a call to come in, and then prints the first "login:" prompt. When someone types in a login id, it exec's /etc/login (or /bin/login) with the string typed by the user as its argument. /etc/login validates the user (makes sure he types in the correct password) then takes care of some other login accounting, then exec's the user's login shell as listed in /etc/passwd.