Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!lll-tis!helios.ee.lbl.gov!nosc!humu!uhccux!lee
From: lee@uhccux.uhcc.hawaii.edu (Greg Lee)
Newsgroups: comp.unix.wizards
Subject: Re: "tip" leaves device file exclusively open
Message-ID: <2658@uhccux.uhcc.hawaii.edu>
Date: 19 Nov 88 14:56:41 GMT
References: <137@abekrd.UUCP>
Organization: University of Hawaii
Lines: 14

From article <137@abekrd.UUCP>, by garyb@abekrd.UUCP (Gary Bartlett):
" We  are  having  a  problem  with "tip" on a  Sun 3/50  running  Sun UNIX 4.2
" Release 3.4.  At the  completion  of some calls,  after  trying to disconnect
" from the line/modem,  the  command  hangs.  Killing  it with 'intr' or 'quit'
" results in the modem  device  being left  exclusively  open,  with the result
" that no other process including our regular uucp links can access the device.

I have occasionally had to kill off a tip and, after removing the lock
file been left with the port unusable -- e.g. tip says 'all devices busy'.
I stumbled on this fix: become superuser and dump a character to the
device.  'echo a >/dev/ttyb' or something similar.  (But maybe this
magic is only locally efficacious.)

		Greg, lee@uhccux.uhcc.hawaii.edu