Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!uunet!cs.dal.ca!iisat!kevin
From: kevin@iisat.UUCP (Kevin Davies)
Newsgroups: comp.mail.uucp
Subject: Re: Bidirectional Modem Lines under SunOS 4.0.1
Message-ID: <433@iisat.UUCP>
Date: 14 Apr 89 14:10:18 GMT
References: <160@osc.COM> <743@key.COM> <2209@laidbak.UUCP> <3834@ficc.uu.net>
Organization: International Information Service, Dart., NS
Lines: 21

In article <3834@ficc.uu.net>, peter@ficc.uu.net (Peter da Silva) writes:
> In article <1423@auspex.auspex.com>, guy@auspex.auspex.com (Guy Harris) writes:
> > >Then utmp is screwed up,
> > Not if the program that fires up "login" (e.g., "ct") knows enough to
> > clear the login entry (which "ct" appears to do).
> 
> init execs getty; getty execs login; login calls back and execs the real
> login. There's some reason I have to have the parent of 'sh' be init, though
> I don't recall what it was, it didn't work if it wasn't done that way.

The parent of 'sh' has to be init, because that is the only indication that
the program has that it is the login shell as apposed to a shell called
by another program/shell.

I suspect it is also the one that sends hangup signals to all other processes
in the same process group etc.

-- 
Kevin Davies		International Information Service (IIS)
UUCP:  {uunet,utai,watmath}!dalcs!iisat!kevin
Bitnet/Uucp: kevin@iisat.uucp	 Arpanet: kevin%iisat.uucp@uunet.uu.net