Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!questor!lclarke
From: lclarke@questor.wimsey.bc.ca (Lawrence Clarke)
Newsgroups: comp.sys.next
Subject: Re: Kermit/Tip Device Locking
Message-ID: <6Xq3Z1w164w@questor.wimsey.bc.ca>
Date: Mon, 08 Apr 91 08:35:40 PDT
References: <1991Apr7.232257.7292@wam.umd.edu>
Organization: Questor - Free Internet/Usenet*Vancouver*BC::+1 604 681 0670

mikec@wam.umd.edu (Michael D. Callaghan) writes:

> Allow me to explain the situation:
> 
> tip works on /dev/cub, but not /dev/cua
> Kermit doesn't work on either, unless from root
> Kermit only works from root on /dev/cub, not /dev/cua
> 
> When I say "doesn't work," I mean that I get "Device Busy" error.
> Tip to /dev/cua responds with:
> 	Device Busy
> 	Link Down
> 
> Both problems ocurred under NS2.0 on the 030 AND the 040 boards.
> 
> Kermit's permissions look like the following:
> 	---s--x--x  1 uucp     uucp      372236 Jan  5 13:18 kermit*
> 

If you've installed a FAX modem, there should be a daemon program running
type
ps -ax
and look for a line that says " Fax_Daemon Local_Fax_Modem "
then type
kill -KILL pid#

Then try tip or kermit again. The problem is the Fax_Daemon is lck-ing
out the serial port that it's on.

> Any suggestions?


 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *  lawrence_clarke@questor.uucp  |  c/o TRIUMF Operations Group     *
 *  larry@erich.triumf.ca         |  University of British Columbia  *
 *  Compuserve: 70441,1776        |  4004 Wesbrook Mall              *
 *  Phone: +1 604 275-5902        |  Vancouver, British Columbia     *
 *  FAX:   +1 604 275-4184        |  Canada  V6T 2A3                 *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *