Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utcs.UUCP
Path: utzoo!utcs!bjf
From: bjf@utcs.UUCP (Bruce Freeman)
Newsgroups: net.unix-wizards
Subject: On 4.2BSD be careful with /bin/login
Message-ID: <223@utcs.UUCP>
Date: Thu, 22-Nov-84 15:04:19 EST
Article-I.D.: utcs.223
Posted: Thu Nov 22 15:04:19 1984
Date-Received: Thu, 22-Nov-84 15:28:36 EST
Organization: University of Toronto - General Purpose UNIX
Lines: 12

About two weeks ago we made the change to /bin/login of having it check
that its parent process id was 1. It is important on 4.2 systems that you
put this check in the right place since /bin/login is invoked by servers
such as rlogind and telnetd whose process id's are certainly not 1!
We found out quite quickly that we put the test in the wrong place (the first
line in main()) thereby preventing rlogin from working to our system.
However I soon realized my mistake and I moved the check further down after
it has been determined that the person logging in is not doing so from a
server. Everything now seems to work fine, one can use rlogin but one can't
type (login foo). Programmer 1, 4.2 0.
-- 
Bruce Freeman	University of Toronto	{decvax|ihnp4|utzoo}!utcs!bjf