sstaton@well.sf.ca.us (Steven R. Staton) (07/28/90)
:a I'm trying to get UUCP on the Cube to call the WELL in Sausilito, CA. Things are not as rosy as I'd like. I get the following chatter in debug mode while trying to send a single mail message to dhawk!well by running uucico after sending the mail message (from the NeXT Mail.app). 8 deltos!#/usr/lib/uucp/uucico -r1 -swell -x4 root well (7/20-15:08-1949) DEBUG (Local Enabled) root well (7/20-15:08-1949) NO CALL (RETRY TIME NOT REACHED) RETRY TIME (600) NOT REACHED root well (7/20-15:08-1949) continuing anyway (debugging) finds (well) called getto: call no. ttyb for sys well Using DIR to call Opening /dev/ttyb login called wanted """" got: that wanted "in:" ATDT14153328649 CONNECT FAST well ()login:got: that wanted "word:" uudeltos Password:got: that root well (7/20-15:08-1949) SUCCEEDED (call to well ) msg-ROK Rmtname well, Role MASTER, Ifn - 5, Loginuser - root rmesg - 'P' got Ptfg wmesg 'U' g Proto started g protocol g root well (7/20-15:08-1949) OK (startup ttyb 9600 baud) *** TOP *** - role=MASTER sstaton well (7/20-15:08-1949) REQUEST (S D.deltosB0002 D.deltosS0002 sstaton) expfile type - 0, wrktype - S wmesg 'S' D.deltosB0002 D.deltosS0002 sstaton - D.deltosB0002 0666 rmesg - 'S' got SY PROCESS: msg - SY SNDFILE: sent data 359 bytes 0.04 secs rmesg - 'C' pkcget: alarm 4001 pkcget: alarm 7002 pkcget: alarm 10003 pkcget: alarm 13004 pkcget: alarm 16005 pkcget: alarm 19006 pkcget: alarm 22007 pkcget: alarm 25008 pkcget: alarm 28009 pkcget: alarm 31010 ...After that, I killed the uucico job after waiting over ten minutes and watching the alarm counter continue to rise by 3001 each time. What is this ``pkcget: alarm'' message trying to tell me? My system is a 12Mb cube with an original TELEBIT Trailblazer connected to the B serial port with a cable provided by DataViz for their MacLink- Plus product. It seems to do hardware handshake, but I could be mistaken. I've set the modem's DTR to hang up (S52=1) and it does work correctly. The problem seems to have something to do with the file transfer part of the call. The ``S D.deltosB0002'' command results in the file being sent but the WELL doesn't seem to respond that it received the file. Could this be a protocol problem? My hostname is correct, I'm logging into the right UUCP account on the WELL. This uucicp command was run from root, which I don't think is a problem. Steve Staton * Deltos Fleet Computing * !apple!well!sstaton BIX:sstaton
jacob@gore.com (Jacob Gore) (07/29/90)
/ comp.sys.next / sstaton@well.sf.ca.us (Steven R. Staton) / Jul 28, 1990 / > What is > this ``pkcget: alarm'' message trying to tell me? A timeout. Quite possibly, a deadlock due to bad flow control. > My system is a 12Mb cube with an original TELEBIT Trailblazer connected > to the B serial port with a cable provided by DataViz for their MacLink- > Plus product. It seems to do hardware handshake, but I could be mistaken. Not on a NeXT port. UUCP is a packet protocol that doesn't need flow control, and can actually be screwed up by it. Put your modem into UUCP mode and turn off all flow control (you can do it in the chat script rather than in the TB EEPROM, so that it doesn's interfere with tip/kermit/whatever). Jacob -- Jacob Gore Jacob@Gore.Com boulder!gore!jacob