Subject: Re: NetBSD-1.0: uucp, cu
To: Simon J. Gerraty <sjg@zen.void.oz.au>
From: Phillip F. Knaack <flipk@iastate.edu>
List: current-users
Date: 11/10/1994 16:11:12
>Is anyone else having a problem with uucp under 1.0?

>I can dial into this system ok as a user,  and using kermit I can
>dial out ok... But cu and uucico fail once carrier is asserted.

For several months we used cu to make an initial connection for SLIP,
dialing from one 1.0-BETA machine to another. We had these results as
well. Often it would take anywhere from 4-10 consecutive tries to get a
connection to continue living after carrier.

Now, having started using point-to-point instead, we have virtually
eliminated that problem (at first we thought it was a hardware or
software problem with the answering computer). We are of the opinion that
cu is just one big bad broken program.

Of late we have also had the problem where cu would not talk to the
modem at all. Connect scripts would timeout waiting for the inital "OK",
and doing ``cu -ltty02 -s38400'' would say ``Connected'' and hang for
the rest of its life. For some odd reason a hard reboot would always fix
it (for a while).

I have made an attempt to track the problem down, however I'm quite sure
that I lack the expertise to find it. Any advise or suggestions anyone
might have would be appreciated. Most especially, where I might look .. 

As much as I want to avoid starting a ``Me too, Me three'' thread, I
would like in on any solutions too .. ;)

Cheers,
Phil

>--sjg
--
Phil Knaack			                           flipk@iastate.edu
WGA, Sociology Department	Student Development Group  flipk@cs.iastate.edu
Iowa State University		Project Vincent, ISU       flipk@vorpal.com