mhw@fithp.uucp (Marc Weinstein) (03/13/91)
This is a followup to my previous posting on the problem with outgoing
calls on a 3b1.
The uugetty doesn't appear to be going to sleep as it should be when an
outgoing call is placed. If the Dialer script has the modem echoing
things back, the uugetty sees this and echoes them back to the modem,
creating an endless cycle. If the echo isn't turned on, then I don't
see a problem until I start talking to the remote system. When it
starts echoing login: and password: back, the uugetty is seeing these
and stealing the characters before uucico sees them, so the login fails.
One interesting thing I noticed...If the Dialer script has the modem
turning local echo on, then the initial attempt by uucico to call out
fails, because the modem and the PC start echoing Returns back and forth
at each other. However, eventually the uucico times out, and then the
second attempt to dial out is preceeded by "set interface UNIX" which
I don't see the first time. This attempt is successful - no cyclic
echoing, and the Dialer script succeeds.
Two questions for you neters: 1) Why isn't the uugetty going to sleep
properly? 2) Why is the second attempt by uucico successful, and could
I get this "set interface UNIX" to be enabled during the FIRST attempt
by uucico?
Just to fill in from last time, this setup, using the Hayes setup
described on the net some time ago, worked fine on 3.5. I recently
upgraded to 3.51m (FIX DISK 2.0) and moved to a 3b1, and I now have
this problem.
Any ideas?
--
Marc Weinstein
{simon,royko,tellab5}!linac!fithp!mhw Elmhurst, IL
-or- {internet host}!linac.fnal.gov!fithp!mhw