Can't cu with mgetty(+fax) v1.0.0

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Ed Huott wrote:
> I'm having trouble getting the cu program from v1.06.1 of the Taylor
> UUCP package to work with mgetty-1.0.0 (mgetty+fax). Before installing
> mgetty (I was using uugetty), cu worked fine with the dial-out port set
> to
> /dev/cua2.
> 
> After installing mgetty, trying to dial out with cu yields an error -
> something to the effect of "All ports busy." 

Yes. This is what the mgetty docs say.

> After changing the port
> configuration file to use /dev/ttyS2 instead (as instructed in the
> mgetty docs), cu seems to able to open the device, but then hangs;
> characters don't seem to get written/read properly.

This will happen if "cu" and "mgetty" do not agree on the location of the
"LCK..ttyS2" file. Most likely, cu will put it into /var/spool/uucp/ and
mgetty will check for it in /var/locks/. Thus, mgetty will assume that the
characters on the modem line are part of an incoming "RING" and garble
everything.

> Here is a sample cu session with debugging turned on that illustrates
> this behavior (a ^C was used to terminate the session):
> 
> # ./cu -d modem
> ./cu: fconn_open: Opening port modem (default speed)
> ./cu: fconn_set: Changing setting to 0, 0, 2
> ./cu: fcsend: Writing "ATZ\r" sleep

*modem*? I thought you were talking about "ttyS2"? Do not ever (!!) use
/dev/modem unless mgetty is *ALSO* using /dev/modem!!

gert

-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-3545980     gert.doering@physik.tu-muenchen.de
.