Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!xanth!nic.MR.NET!hal!ncoast!allbery From: allbery@ncoast.ORG (Brandon S. Allbery) Newsgroups: comp.mail.uucp Subject: Re: Bidirectional Modem Lines under SunOS 4.0.1 Message-ID: <13597@ncoast.ORG> Date: 22 Apr 89 01:51:18 GMT References: <160@osc.COM> <743@key.COM> <2209@laidbak.UUCP> <1423@auspex.auspex.com> <3834@ficc.uu.net> <1438@auspex.auspex.com> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.mail.uucp Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 23 As quoted from <1438@auspex.auspex.com> by guy@auspex.auspex.com (Guy Harris): +--------------- | >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. | | In that case, your "sh", or something, is broken. The SunOS version | doesn't have this problem; otherwise, neither "rlogin" nor TELNET would | work very well, since the login shell on a remote login is a child of | the rlogin or TELNET daemon, not a child of "init". +--------------- May I suggest that the real reason it broke was that the login shell wasn't leader of the process group that owns the terminal? This would likely cause various nasty things to happen wrt. signals, perhaps (I'm not well-versed in this subject, but it seems quite possible) especially job control. ++Brandon -- Brandon S. Allbery, moderator of comp.sources.misc allbery@ncoast.org uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu Send comp.sources.misc submissions to comp-sources-misc@ NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser