Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!rice!uw-beaver!milton!ogicse!intelhf!ichips!inews!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.uucp
Subject: Re: getting UUCP expect/send scripts working
Message-ID: <1991Mar11.200146.10618@chinet.chi.il.us>
Date: 11 Mar 91 20:01:46 GMT
References: <1991Mar08.054130.12990@jpradley.jpr.com> <1991Mar09.213352.3942@chinet.chi.il.us> <1991Mar10.193008.3732@jpradley.jpr.com>
Organization: Chinet - Chicago Public Access UNIX
Lines: 26

In article <1991Mar10.193008.3732@jpradley.jpr.com> jpr@jpradley.jpr.com (Jean-Pierre Radley) writes:

[re: cu chatting]
>Reread what I wrote. One can set up two entirely Systems files, e.g.
>Systems.cico and Systems.uucp. Thus, a chat script be run by uucico would
>differ from a chat script to be run by cu.
>Do you have a Sysfiles.eg in your /usr/lib/uucp?

Yes, I have Sysfiles, and I have run cu and uucico both with the same
and different Systems files in different circumstances.  In no case
has cu ever executed the login script found in its Systems file even
if Sysfiles specified that it was for cu's use only.  I'm
running AT&T SysVr3 (and previous releases did the same).  Perhaps
other versions are different.  I would like to have that functionality
and have occasionally faked it with the "modem-class" specification
in the Systems file selecting a Device entry which selects a Dialer
script which performs the login chat as well.  This works but it is
somewhat contorted in that you have to repeat the Device entry for
every device capable of making the connection and this becomes difficult
if these devices might need different scripts for the dialing portion.  
I would prefer for it to work as you say, even though you would be
forced to use different Systems files for cu and uucico to make
cu systemname useful.

Les Mikesell
  les@chinet.chi.il.us