Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!uwmcsd1!ig!agate!pasteur!ames!lll-lcc!unisoft!gethen!bdt!david
From: david@bdt.UUCP (David Beckemeyer)
Newsgroups: comp.unix.microport
Subject: Re: C-Kermit
Message-ID: <188@bdt.UUCP>
Date: 21 Mar 88 18:58:04 GMT
References: <321@w3vh.UUCP>
Reply-To: david@bdt.UUCP (David Beckemeyer)
Organization: Beckemeyer Development Tools, Oakland, CA
Lines: 19
Keywords: Microport System V/AT

In article <321@w3vh.UUCP> rolfe@w3vh.UUCP (Rolfe Tessem) writes:
[ some deleted ]
>For that matter, I've been unable
>to terminate a session gracefully after a file transfer, and have to
>resort to quitting or killing it from root. That leads to the /dev/tty
>line being left with wierd ownerships and permissions, leading to 
>further aggravation.  

Usually, the regular "Control-\ c" gets me back to the Kermit prompt, and
then "exit" cleans it up.  But I have had the uport distributed kermit
"lockup" inexplicitly sometimes too.  Although you don't actually have to
be "root" to kill it, just login as the owner of the kermit process; but
you still have to manually clean up the tty line as you mention.

-- 
David Beckemeyer			| "To understand ranch lingo all yuh
Beckemeyer Development Tools		| have to do is to know in advance what
478 Santa Clara Ave, Oakland, CA 94610	| the other feller means an' then pay
UUCP: ...!ihnp4!hoptoad!bdt!david 	| no attention to what he says"