andrewd@cs.tamu.edu (Andrew Ted Duchowski) (04/07/91)
Hi,
I just hooked up a DoveFax modem (2400 data/9600 fax) to my
'040 cube. Everything seemed to be ok, I managed to dial
out once. Then, every time I try to tip again (or even
go through kermit) I get the message:
device /dev/cua busy
link down
It seems to me that there's a lock on /dev/cua somewhere
that got put on it when I first dialed out, and
when I disconnected, the lock never got released. But
I don't know where this lock may be or how to get rid
of it. I thought there may be a file somewhere in
/usr/spool/uucp that resembled a LOCK file, but couldn't
find anything like that. Can someone help me?
This is what I did so far:
1. hooked the modem to serial port A
2. the cable seems ok since I managed to dial out once
3. I put in Steve Boker's script:
#! /bin/sh -u
PIDS=`ps -ax | bm getty | grep -v bm | awk '{print $1}'`
kill -TERM $PIDS
kill -HUP 1
into crontab. I also tried executing it manually thinking
that it would eliminate the lock on /dev/cua
4. I editted /etc/ttys and editted the ttyda entry to be
ttyda "/usr/etc/getty std.2400" vt100 on
However I use /dev/cua for dial out. I think the above is
mostly intended for dial in only.
5. For tip, I editted /etc/remote and basically copied all
lines I needed and replaced 1200 to 2400 where appropriate.
6. I changed permissions on /dev/cua including:
chmod a+rw cua
chmod a+s cua
chmod a+t cua
thinking that the sticky bit had to be set. BTW, I'm not
sure which permissions need to be set for /dev/cua - can
someone shed some light on this?
What am I missing/did wrong?
Thanks in advance for any suggestions. If you're going
to post a response, please also cc me a copy to andrewd@cs.tamu.edu.
Andrew.
--
-------------- Not an Official Texas A&M University Document --------------