Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!think.com!mintaka!ogicse!uidaho!tamaluit!pbickers
From: pbickers@tamaluit.phys.uidaho.edu (Paul Bickerstaff)
Newsgroups: comp.sys.mips
Subject: uu-status and modem on Magnum/digiboard port
Message-ID: <1991Jun06.190435.24051@groucho>
Date: 6 Jun 91 19:04:35 GMT
Sender: @groucho
Reply-To: pbickers@tamaluit.phys.uidaho.edu (Paul Bickerstaff)
Organization: mrc
Lines: 79
Nntp-Posting-Host: tamaluit.phys.uidaho.edu

I have a minor problem which I can't fathom:   We have a
Magnum 3000 running RISCos 4.51 and I've put a Practical Peripherals
(Hayes compatible) modem on one of the ports of a 16-port Digiboard
card (RJ45 - DB25 straight through cable).  I've set uugetty running
on this port (/etc/inittab entry):

d3:234:respawn:/usr/lib/uucp/uugetty -h -t 60 -r ttyd3 dm2400 none LDISC0

and /etc/gettydefs entry:

dm2400# B2400 CLOCAL MDMBUF # B2400 CLOCAL MDMBUF SANE TAB3
#\r\n\n$HOSTNAME login: #dm2400

(and have tried HUPCL here without it curing the problem).

The problem is that the port gets locked and stays locked.  More precisely,
the first time someone dials in (after I change things) the port does not
lock  (!! which I'm sure it should) but only locks when the user exits and
stays locked thereafter.  (At least the lock file only appears in
/usr/spool/locks
when the user exits and stays there until I step in and remove it.) My belief
is that the port should be locked when in use and not otherwise.

Now this is only a minor problem because the modem is desired mainly for
dial-ins and it appears to work fine for this purpose despite the above
behaviour (though see the remarks below on ownership).  However, I would
like the modem available for dialing out, if desired, and besides, the
following
repeated mail messages to root are driving me nuts:

        Subject: uu-status
        Apparently-To: uucp

        LCK..ttyd3: 3443
         F S     UID   PID  PPID  C PRI NI     ADDR     SZ   WCHAN    STIME TTY
     TIME COMD
        10 S    root  3443     1  0  28 20 801103e8     71 c013f740
22:35:30 tty
d3    0:00 /usr/lib/uucp/uugetty -h -t 60 -r t

I know that if I were to be satisfied with just dial-ins I could just
run getty on
the port but I feel that would be an unsatisfying solution :-)  (if it's
a solution
at all -- I have n't tried it.)

Some further info: 

the device ownership and permissions are being interfered with; currently 
(with the thing locked) we have:

% ls -l /dev/ttyd3
crw--w--w-   1 uucp     theory    32,  3 Jun  6 08:29 /dev/ttyd3

I initially set the permissions to 664 and the group to daemon, in accordance
with recommended (Nemeth et al.) practice.  Theory is the group of the
person who last logged in via the modem.  (Don't know what happens if
somebody in another group trys to dial-in.  The problem is not likely to
arise :-) ) 

I also have added these entries to the Devices file:

Direct ttyd2 - 1200 direct #ups
Direct ttyd3 - 2400 direct
#ACU cul3 cua3 2400 hayes
#ACU cul3 cua3 1200 hayes
ACU ttyd3 - 2400 hayes

but don't think that is relevant to the present problem.

If anybody knows what I'm overlooking I'd sure appreciate the magic
recipe.

Many thanks in advance,
Paul

Paul Bickerstaff                 Internet: pbickers@tamaluit.phys.uidaho.edu
Physics Dept., Univ. of Idaho    Phone:    (208) 885 6809
Moscow ID 83843, USA             FAX:      (208) 885 6173