Xref: utzoo comp.mail.uucp:3082 comp.unix.questions:13246
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!cheers!exodus
From: exodus@cheers.UUCP (Greg Onufer)
Newsgroups: comp.mail.uucp,comp.unix.questions
Subject: Re: uucp and parity checking
Message-ID: <235@cheers.UUCP>
Date: 4 May 89 07:28:00 GMT
References: <1108@wpg.UUCP>
Followup-To: comp.mail.uucp
Organization: Cheers Bar & Grill
Lines: 30

In article <1108@wpg.UUCP>, russ@wpg.UUCP (Russell Lawrence) writes:
> Unlike most systems that we communicate with, 'xyz' does parity
> checking on their ports.  Could this be the cause of our problem, and
> if so, can anyone suggest a work around?  'xyz' does *NOT*
> run HDB and I don't think they're too excited about changing the
> port definitions in their gettydefs file in order to conform to
> our expectations.

This is mostly lore passed around by those who saw it once, a long
time ago....

The first thing to put in your expect-send sequence is:

	"" P_ZERO
	(expect nothing, set parity to none)

or replace P_ZERO with P_ODD, P_EVEN, or P_ONE, whichever works.
I had to use these with lll-winken after it was upgraded to a newer
machine.  Symptoms: immediately after logging in, the connection would
time out... thanks to an omniscient administrator at llnl, these undocumented
features of BSD uucp were made known to me.  They worked with my UUCP also.

Good luck...

Cheers,
Greg

-- 
Greg Onufer .. University of the Pacific .. Focus Semiconductor
.. greg@cheers.uucp .. cheers!greg@lll-winken.llnl.gov .. 209-957-3963