Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!van-bc!twg!bill
From: bill@twg.bc.ca (Bill Irwin)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Does uu/ungetty force S0=1 for dial out lines?
Message-ID: <604@twg.bc.ca>
Date: 4 Feb 91 06:28:42 GMT
References: <563@twg.bc.ca> <1810@chinacat.Unicom.COM> <578@twg.bc.ca> <1991Jan31.070143.28223@odbffm.incom.de>
Reply-To: bill@twg.bc.ca (Bill Irwin)
Organization: The Westrheim Group, Vancouver, B.C., Canada
Lines: 26

oli@odbffm.incom.de (Oliver Boehmer) writes:

:In <578@twg.bc.ca> bill@twg.bc.ca (Bill Irwin) writes:

:>I have come to the realization that the &hayes2400 entry in
:>Dialers was running whenever the port was enabled.  By specifying
:>the hayes1200 dialer, which doesn't set S0, the problem is gone.

:wrong. The entry &hayes2400 is executed when the port is brought up to
:default state, after the connection is finished. uucp executed the
:hayes2400-line (w/o &) via uuchat prior to dialing. Afterwards, it executes
:the &hayes-line.

What you said is true.  What I said is also true.  When I had the
line configured for the hayes2400 dialer, I simply disabled and
enabled the port.  This action turned the AA light back on.  It
seems that whenever another process is finished with the port
, or the port is enabled, the uugetty runs uuchat which looks for
an "&" version of the dialer entry.

:Oliver Boehmer, Frankfurt, Germany    uucp:   oli@odbffm.incom.de
-- 
Bill Irwin    -       The Westrheim Group     -    Vancouver, BC, Canada
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
uunet!van-bc!twg!bill     (604) 431-9600 (voice) |     Your Computer  
bill@twg.bc.ca            (604) 430-4329 (fax)   |    Systems Partner