Sys V uugetty problem

[Lars Tunkrans]

In article <20286 at bcsaic.UUCP> carroll at bcsaic.UUCP (Jeff Carroll) writes:
>
>	I have a modem on a serial port on my System V/386 box which I
>would like to use for dialout as well as dialin. getty works fine, in
>the usual expected way, but when I edit /etc/inittab to call uugetty
>rather than getty, something strange happens.
>	uugetty handles incoming calls OK, but when I try to use cu to
>dial out, it doesn't seem to be able to open the tty line. Running   
>cu -d -ltty00 the system tells me "CAN'T ACCESS DEVICE".
>	Any ideas?
 
   My inittab looks like this :

    14:23:respawn:/usr/lib/uucp/uugetty -t 30 -r tty14 2400 vt100

   And the Systems file:

    modem Never modem 2400

   And the Devices file:

    modem tty14 - Any direct \D

   If this config doesn't work, you probably have a RS232 interface
problem.  My DRS300 wants DCD, DSR and CTS high as a condition to
transmit anything on the interface. If the carrier is missing it does
indeed behave as you describe. It is possible to dial in to the system
without setting DCD high permanently because the carrier is raised by
the incomming call.

   If you want to do  " cu nodename " you need to do a more detailed
config on a per system basis including the Dialers file. The above
config allows you to connect to the modem and use its AT-commands if you
are using Hayes compatible modems.
-----

-- 
The ICL DRS6000    | Lars Tunkrans  DRS Systems support  Phone +46 (0)76096368.
Series has the     | UUCP: {uunet,mcsun,munnari,cernvax,diku,inria,prlb2,tut,ukc
first UNIX System  | ,unido} !sunic!iclswe!lars   " History teaches us that man 
V Release 4 Port.  |  does'nt learn from history "  Herodotos  300 B.C.