Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!zardoz.cpd.com!dhw68k!fedeva!dynasys!jessea
From: jessea@dynasys.UUCP (Jesse W. Asher)
Newsgroups: comp.dcom.modems
Subject: TB+ doesn't kill user's sh?
Message-ID: <37@dynasys.UUCP>
Date: 9 Feb 90 01:06:13 GMT
Reply-To: jessea@dynasys.UUCP (Jesse W. Asher)
Organization: Dynasys:  Consulting for the Future.
Lines: 11

I've got an internal TB+ and when someone logs off after having
called in, the user's shell doesn't get killed.  I've been told
that S53 is the culprit I should look at, put I've tried everything
I can think of.  I normally have it set up for S53=4.  Why is it
not killing those processes and how can I get it to stop?  Thanx
for the help.


-- 
Jesse W. Asher - Dynasys - (901)382-1705       Internet: root@dynasys.UUCP
6196-1 Macon Rd., Suite 200, Memphis, TN 38134     UUCP: uunet!dynasys!root