From: tbuck@teal.csn.org (Timothy E. Buchanan)
Subject: uucico woes
Organization: Colorado SuperNet, Inc.
Date: Sat, 22 Aug 1992 16:28:02 GMT

I've written before about uucico problems with C386 on my bitty 
box. What drives me crazy is the Heisenburg nature of the bug; 
yesterday it worked fine, sending mail, receiving files, today back 
to calling, then hanging. And I didn't do anything in the meantime 
(I know this is a cliche).
 
Here's an excerpt from a debug file-
 
Thinking of calling system: csn
lsys_value( Schedule ) = Any
checktime(Any) = Ok to call now -- Forced
Opening Log File: /usr/spool/uucp/.Log/uucico/csn
Just created lock: /usr/spool/uucp/LCK..csn
Mstate = S
08/22 08:48:24 [csn]: Calling site csn {473} (V4.0.04S)
lsys_value( Device ) = ACU
lsys_value( Speed ) = 19200
lsys_value( Phone ) = xxxxxxxxx
Trying to connect at speed 19200
Calling phone# xxxxxxxxx
Devices Line: {ACU com4l com4r 19200 supra}
Parsed Devices Entry:
        Connection Type = ACU
        Local Line  = com4l
        Remote Line = com4r
        Baud Rate   = 19200
        Brand       = supra
ldev_value( Connection Type ) = ACU
ldev_value( Local Line ) = com4l
ldev_value( Remote Line ) = com4r
ldev_value( Baud Rate ) = 19200
ldev_value( Brand ) = supra
Just created lock: /usr/spool/uucp/LCK..5.3
08/22 08:48:26 [csn]: Disabling tty line com4r
SIGALRM received     #What is this?????
hangup: (level2) about to drop line.
Lockrm: PID verify successful, removing lock.
08/22 08:49:44 [csn]: Lockrm: PID verify successful, removing lock.
Just unlocked: /usr/spool/uucp/LCK..5.3
08/22 08:49:44 [csn]: Enabling tty line com4r
08/22 08:49:46 [csn]: Dial failed, ACU Problem {473}
08/22 08:49:46 [csn]: Modem says     Annex Command Line Interpreter \
*   Copyright 1991 Xylogics, Inc.  
dcpundial: about to call hangup().
hangup: (level2) about to drop line.
Mstate = Y
dcpundial: about to call hangup().
hangup: (level2) about to drop line.
08/22 08:50:02 [csn]: Removing remote site lock
Lockrm: PID verify successful, removing lock.
08/22 08:50:02 [csn]: Lockrm: PID verify successful, removing lock.
Just unlocked: /usr/spool/uucp/LCK..csn
08/22 08:50:02 [csn]: Abnormal completion {473}
Closing Log File: /usr/spool/uucp/.Log/uucico/csn
Mstate = I
                        
Udo Monk suggested I use com4fr and also asked if I have a 16550AFN 
chip (yes to that). When I place com4fr in /etc/ttys and run kill 
quit 1 I get an unable to create device. Also, com4r was being used 
successfully ytdy.
 
I don't understand why com's are used in /ttys /modemcap /L-devices 
when C386 uses the asy drivers. At any rate, I reran asypatch, w/ 
19200 baud set in default/async and choosing lrif in the options 
for ASY03. No joy there either.
 
Are com's just links to asy's in C386? bob@mwc.com suggested I run 
mknod on the com devices. I know the major number for com4 should 
be 5 but what should I use for the minor number. Why can't I cp 
these files to another dir? How can this work sometimes but fail 
another?
 
Lastly, when the system was working, mail bob@mwc.com would send 
via my smart-host and receive mail packets, but these stayed in 
/usr/spool/uucp/csn and were not delivered. Why? I have aliases 
written. Lexicon mentions a /.forward file, but neglects to give an 
example. Is this needed, if so what is the format?
 
Appreciate any help with this very frustrating problem.
 
Timothy.
                                       

Newsgroups: comp.os.coherent