Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!wuarchive!uunet!bria!mike
From: mike@bria.AIX (Mike Stefanik/78125)
Newsgroups: comp.unix.admin
Subject: Re: SG Iris, modems
Message-ID: <293@bria.AIX>
Date: 31 Dec 90 01:36:16 GMT
References: <12706@medusa.cs.purdue.edu> <1990Dec12.003902.4650@smsc.sony.com>
Distribution: usa
Organization: Briareus Corporation, Los Angeles, CA
Lines: 33

> In article <12706@medusa.cs.purdue.edu> mhh@lisa.cs.purdue.edu (Matthew Harper) writes:
> >6.) cu -s 1200 -l /dev/ttym2
> >
> >After running cu, we got the follwoing error:
> >ERROR - Can't Access Device
> >
> >Could anybody tell me why this isn't working and what I need to do 
> >(It is running UNIX System V Version 2.0) to be able to communicate with
> >the modem.
> 
> Check the permission on /dev/ttym2.  It needs to be r/w by world, or better,
> own by uucp and in the uucp group.  cu runs suid to uucp (on most system
> I am familiar with).

The problem is with the "/dev/ttym2" -- more than likely you meant "ttym2",
which is how it should be in the Devices file (this is assuming you're using
HoneyDanBer UUCP).  The /usr/lib/uucp/Devices entry could look like:

      Direct ttym2 - 1200 direct

The above stated is correct, though: your device should be owned by both 
user and group "uucp".  So you really want the command to look like:

      $ cu -s 1200 -l ttym2

It may be necessary to disable getty on ttym2 as well by removing the
respawn getty on that port from inittab and doing a telinit -q.

Hope that helps.
-----------------------------------------------------------------------------
Michael Stefanik, Systems Engineer (JOAT), Briareus Corporation
UUCP: ...!uunet!bria!mike
"If it was hard to code, it should be harder to use!"