🚀 go-pugleaf

In article <Pine.SCO.3.90.941007185717.22070A-100000@wshb>,
Jerry Lopez - WSHB Senior Software Developer - En  <jerry@wshb> wrote:
>I am experiencing trouble with my machine at home running Taylor UUCP
>logging onto a SCO Unix machine.  I seems that the SCO machine is not
>recognizing the carriage returns.  Has anyone experienced this trouble or
>has any idea what might be the problem.

Your problem is probably your scripts.  I had Taylor running fine under
SCO for quite a while but lemme give you some gotcha's:

The SCO uucp implentation is MUCH easier to debug, and the debugging
levels/output is much more sane than Taylor. (For one thing it does not
toss itself automagically in the background like taylor).

The SCO uucico binary can use ATdial or a custom binary dialer to dial
the phone and will get an intelligent result code back from the dialer
as to the status of the call (rather than just success or failure) and
will walk down a list of ACU's trying again if it gets back the likes of
'NO DIALTONE', or no response in the event of a stuck line or dead
modem.  Taylor will simply try the same dead modem, over, and over, and
over, ...  as long as it can get a lock file.

Placing time_to_call restrictions in the Taylor configuration will make
the site uncallable if the restriction is in effect.  Even with '-S' on
the uucico line.  This is a severe problem for me because I have several
sites that _I_ wish to POLL _only_ from a crontab entry, and to do it
you need to write a script to change Never to Any in the script file,
and run the poll, then monitor the log, and flip it back after the call
completes.  yuk.

I did have a LOT of problem with the chat scripts also, getting them
right, although the task was not insurmountable, Debugging a chat script
under taylor is like pulling teeth.  Go to the console run one screen on
tail -f Log and the other on tail -f Debug take #3 and uucico -r1 -x9
-Ssite and start flipping between the first two to see what the heck is
happening.  A lot of the problems I had were with response timeouts btw,
requireing strategic placement of \d in the scripts, and adjustment of
the -timeout parms.
-- 
Keith Smith        Digital Designs               keith@ksmith.com
5719 Archer Rd.    PO Box 85       Free Usenet News and Internet Mail Services
Hope Mills, NC 28348-0085         All 28K/14K Modems  (910) 423-4216/7389/7391
Somewhere in the Styx of North Carolina ...         14K-V.32/28K-V.34/28K-V.34

jerry@wshb (Jerry Lopez - WSHB Senior Software Developer - En) writes:

>I am experiencing trouble with my machine at home running Taylor UUCP
>logging onto a SCO Unix machine.  I seems that the SCO machine is not
>recognizing the carriage returns.  Has anyone experienced this trouble or
>has any idea what might be the problem.

The most common problem with SCO Unix is that it apparently flushes
the input buffer after printing the string ``login:''.  Taylor UUCP
generally sends data as fast as possible, and the login name often
gets flushed.  Add a \d or two before the sending the login name.
-- 
Ian Taylor | ian@airs.com | First to identify quote wins free e-mail message:
``A profound tolerance is in the land, a tolerance so profound that it is not
  unlike terror.''  (written in 1958 about the U.S.A.)

Jerry Lopez - WSHB Senior Software Developer - En (jerry@wshb) wrote:
:>I am experiencing trouble with my machine at home running Taylor UUCP
:>logging onto a SCO Unix machine.  I seems that the SCO machine is not
:>recognizing the carriage returns.  Has anyone experienced this trouble or
:>has any idea what might be the problem.

I had a similar problem using uucp from a linux box to a sco box. What I 
found was that in the chat script I had to use a "\n\c" right after 
sending my login name. I set mine up to use the Systems file and here
is an example of what worked for me:

lmscdev Any ACU 19200 5551212 "" \r ogin:--ogin: nuucp\n\c "" \r ssword: pw

hope this helps!

--
--                  /--\   /--\      /--\  |   |  ---  ----  ----  /--\  ||
Steve Miller        |      |  |      |     |___|   |   |_    |_    \__   ||
Kansas City, MO     | -\   |  |      |     |   |   |   |     |        \  ||
stevem@tyrell.net   \__/   \__/      \__/  |   |  _|_  |___  |     \__/  oo

In article <Pine.SCO.3.90.941007185717.22070A-100000@wshb>,
Jerry Lopez - WSHB Senior Software Developer - En  <jerry@wshb> wrote:
>I am experiencing trouble with my machine at home running Taylor UUCP
>logging onto a SCO Unix machine.  I seems that the SCO machine is not
>recognizing the carriage returns.  Has anyone experienced this trouble or
>has any idea what might be the problem.
>
>
>                        Jerry Lopez -- WSHB Engineer 
>                WSHB - An International Broadcast Station of   
>           Herald Broadcasting Syn., Inc., Cypress Creek, SC, USA
>                            jerry@wshb.csms.com
>
>-- 
>                        Jerry Lopez -- WSHB Engineer 
>                WSHB - An International Broadcast Station of   
>           Herald Broadcasting Syn., Inc., Cypress Creek, SC, USA
>                            jerry@wshb.csms.com


Excuse me, I don't usually include other people's signature blocks in my
replies, but I did so here to point out that yours, Jerry, is appearing twice.

SCO's binaries flush the input buffers when throwing up the login: prompt, so
what you need in your Taylor chat script is some delay.
I use this chat script for calling any SCO machine:

	chat ogin:-BREAK-ogin:-BREAK-ogin: \d\L word: \P
-- 
Jean-Pierre Radley   jpr@jpr.com     XC custodian    Sysop, CompuServe SCOForum