Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!tut.cis.ohio-state.edu!ucbvax!SODA.BERKELEY.EDU!glass
From: glass@SODA.BERKELEY.EDU
Newsgroups: comp.mail.uucp
Subject: uucp config only works w/ -x5 or higher
Message-ID: <9012301143.AA12314@soda.Berkeley.EDU>
Date: 30 Dec 90 11:43:10 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 25


Scenario: 3/60 running 4.1 SunOS HDB UUCP polling an apollo running
	  HDB.  The apollo is reachable via an intermediate
	  port selector type device.
system entry for 3/60 --> apollo:
apollo Any ACU 2400 1234567 "" STTY=crtscts quest: foobar gin: nobody
law \c violet \c chine? apollo ser? squish word: nuts

The problem is that uucico's from the 3/60 to the apollo die with 
"BAD READ (expected 'S' got FAIL)" errors unless debugging is set to
-x5 --> -x9 in which case things work fine.  The apollo logs the
problem as "BAD READ (expected ')".

The STTY= stuff is a probable sunism that doesn't change the problem
when removed.

So the question is what is so special about the debugging
information that it lets my configuration succeed where normally it wouldn't?

later,
Adam

Adam Glass                           |Internet: glass@soda.Berkeley.EDU
various roles at Berkeley	     |UUCP: !ucbvax!soda!glass
				     |Coming soon: glass@chaos.org