Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!usc!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!yale!spock!lancelot
From: lancelot@spock.UUCP (Thor Lancelot Simon)
Newsgroups: comp.mail.uucp
Subject: Re: What does k==9 mean?
Keywords: k==9
Message-ID: <1991Jan25.213459.29786@spock.UUCP>
Date: 25 Jan 91 21:34:59 GMT
References: <1991Jan22.213637.20338@sci.ccny.cuny.edu>
Reply-To: lancelot@spock.UUCP (Thor Lancelot Simon)
Organization: Choate Rosemary Hall, Wallingford CT
Lines: 33

In article <1991Jan22.213637.20338@sci.ccny.cuny.edu> jeffrey@sci.ccny.cuny.edu (Jeffrey L Bromberger) writes:

>imsg input<	125U	147g	0\0>got 2 characters
>got Ug
>send 077
>rec h->cntl 077
>bad header (k==9) 077
>pkcget: alarm 4001
>send 077                      <- These lines get repeated
>rec h->cntl 077               <- before each of the following
>bad header (k==9) 077         <- alarms

This looks to me like your bridge is not 8-bit clean.  UUCP is probably getting
a bad character in the header, and timing out (this is what alarm means), then
sending a 077 (I think this is the 'retry' signal), getting another bad header,
and so forth.  The reason the alarm is different each time is because the alarm
number is computed by multiplying the timeout by the number of alarms already
generated and adding the last alarm number (or something like that). 4001 is
usually the first one in any sequence.


>Jeffrey L. Bromberger
>System Operator---City College of New York---Science Computing Facility
>jeffrey@sci.ccny.cuny.edu			jeffrey@ccnysci.BITNET
>	Anywhere!{cmcl2,philabs,phri}!ccnysci!jeffrey



*******************************************************************************
*Thor Simon             * Okay, just a little pin-prick...There'll be no more-*
*lancelot@spock.UUCP    * Aieeeeaaaugh!-but you may feel a little _sick_.     *
*uunet!hsi!yale!lancelot*   ---Pink Floyd                                     *
*******************************************************************************