Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncoast.UUCP
Path: utzoo!linus!decvax!cwruecmp!atvax!ncoast!bsa
From: bsa@ncoast.UUCP (Brandon Allbery)
Newsgroups: net.unix-wizards
Subject: Re: deceptive mail
Message-ID: <419@ncoast.UUCP>
Date: Sun, 18-Nov-84 11:17:14 EST
Article-I.D.: ncoast.419
Posted: Sun Nov 18 11:17:14 1984
Date-Received: Wed, 21-Nov-84 05:16:52 EST
References: <331@uvm-cs.UUCP> <45@uwvax.UUCP> <221@turing.UUCP> <>
Reply-To: bsa@ncoast.UUCP (Brandon Allbery)
Organization: `Stamp Out MicroSoft!' on the North Coast
Lines: 34
Summary: 

> Article <>, from mike@amdcad.UUCP (Mike Parker)
+----------------
| > It is even worse: if you are working at a terminal, somebody comes along
| > and in order to show you something logs in recursively: (login x)
| > then after his login process has finished your identity will be reported
| > as x by programs like who and routines like getlogin().
| 
| Say What!
| 
| If someone comes up to your terminal and types "login name" you
| will be logged out and he will be logged in. If his login process
| "finishes" i.e. he logs out, the system will display a login 
| banner. YOU WILL BE GONE! I'd say whoever did this when you were
| at a terminal walked away without logging off. Are you confusing
| login with su???

Nope.  Typing

% login me

logs out the current user.  What the original message said was:

% (login me)

which forces login to run in a subshell.  I often pull that trick with
newgrp, we lacking sg.

--bsa
-- 
  Brandon Allbery @ North Coast Xenix  |   the.world!ucbvax!decvax!cwruecmp!
6504 Chestnut Road, Independence, Ohio |       {atvax!}ncoast!{tdi1!}bsa
   (216) 524-1416             \ 44131  | E1439@CSUOHIO.BITNET (friend's acct.)
---------------------------------------+---------------------------------------
Forgive; we just had a system crash & lost a month's worth of work and patches.