uucico is eating my outgoing mail!

Lenny Tropiano lenny at icus.islp.ny.us
Thu Oct 19 14:28:33 AEST 1989


In article <1989Oct16.181609.14182 at mccc.uucp> pjh at mccc.UUCP (Pete Holsberg) 
writes:
|>In article <1989Oct14.105712.9505 at ivucsb.sba.ca.us> todd at ivucsb.sba.ca.us 
(Todd Day) writes:
...
|>=anise!todd (10/14-2:46:02) (C,9339,0) REQUEST (S D.aniseBC5662 D.aniseBC5662 todd)
|>=anise!todd (10/14-2:48:25) (C,9339,1) BAD READ (expected 'C' got FAIL)
|>=anise!todd (10/14-2:48:25) (C,9339,1) FAILED (conversation complete)
|>
|>What causes the "BAD READ (expected 'C' got FAIL)"??

Basically when uucico is going through it's handshaking to coordinate between
the different files to send the ("D.*" and "X.*" files), uucico will stop
after each file and wait for an <ACK>nowledgement from the other site.

*** TOP ***  -  role=1, setline - X
Request: icus!D.icus1eac709 --> att!D.icus1eac709 (lenny)
setline - S
wrktype - S
 wmesg 'S' D.icus1eac709 D.icus1eac709 lenny - D.icus1eac709 0666 lenny
rmesg - 'S' got SY
 PROCESS: msg - SY
SNDFILE:
-> 1683 / 1.416 = 1188.5
rmesg - 'C' got CY             
 PROCESS: msg - CY
...
 
		^^ If for some reason the remote site doesn't send back
		   anything, or gets out of sync, or there is noise on the
		   line... several (10 I think) alarm() calls will happen.
		   and eventually it will timeout with the message.
		   BAD READ (expected 'C' got FAIL)

-Lenny
-- 
| Lenny Tropiano            ICUS Software Systems      [w] +1 (516) 589-7930 |
| lenny at icus.islp.ny.us     Telex; 154232428 ICUS      [h] +1 (516) 968-8576 |
| {ames,pacbell,decuac,hombre,sbcs,attctc}!icus!lenny     attmail!icus!lenny |
+------- ICUS Software Systems -- PO Box 1;  Islip Terrace, NY  11752 -------+



More information about the Unix-pc.uucp mailing list