Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!rex!uflorida!novavax!ankh!pax
From: pax@ankh.COM (Garry M. Paxinos)
Newsgroups: comp.unix.i386
Subject: Re: uucico timeout is too short
Message-ID: <271@ankh.COM>
Date: 15 Jan 90 12:39:19 GMT
References: <1990Jan12.230447.2579@virtech.uucp> <1990Jan14.141325.698@virtech.uucp>
Organization: Megasystems, Inc. Delray Beach, FL
Lines: 27
In-reply-to: cpcahil@virtech.uucp's message of 14 Jan 90 14:13:25 GMT

In article <1990Jan14.141325.698@virtech.uucp> cpcahil@virtech.uucp (Conor P. Cahill) writes:
   Yesterday, I posted this message about uucico timeout comming too early.

   In article <1990Jan12.230447.2579@virtech.uucp>, cpcahil@virtech.uucp (Conor P. Cahill) writes:
   > The timeout for uucico to use when waiting for a response should
   > be configurable so that those of us who have modems that use extended
   > handshaking could give it enough time to connect.  

   Since then at least three people had told me about the following solution:

   add \d's to the dial string which impose a delay before the uucico timeout
   starts.

A simpler one, which will also respond faster (as I sent in a message
today to you...) is replace the 'CONNECT' statement (or anyother as
applicable) with  'CONNECT-/c-CONNECT' .  With this approach, you 
won't have any arbitrary amount of fixed delay, if the CONNECT happens
fast you'll catch it, but you'll double you total timeout period on
the slow ones.

Take care,
Garry.
-- 
Internet :  home - pax@ankh.ftl.fl.us   work : pax@megasys.com
USNail   :  3868 NW 21 Ct.  Coconut Creek, Fl 33066
UUCP     :  {gatech!uflorida!novavax, mthvax, attctc, hoptoad}!ankh!pax
VoiceMail:  305-973-8478