Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ki4pv.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!ki4pv!tanner
From: tanner@ki4pv.UUCP (Tanner Andrews)
Newsgroups: net.bugs.uucp
Subject: Calling UUCP with -Xn option for debug
Message-ID: <7024@ki4pv.UUCP>
Date: Thu, 2-Jan-86 20:06:50 EST
Article-I.D.: ki4pv.7024
Posted: Thu Jan  2 20:06:50 1986
Date-Received: Sat, 4-Jan-86 04:43:24 EST
Organization: CompuData South, DeLand
Lines: 36
Keywords: xenix

If you are using UUCP with xenix 3.0(up through 3.0b at least) you will
probably encounter this when someone is trying to UUCP to your site for
the first time.

Repeat by:
Set up a correct system entry to call someone running xenix uucp.  Pick
a line and condition it for output as required.  Use the command
	uucico -r1 -Ssysname -X9

This should provide debugging information.  Problem is that the "-X9"
information is passed along to the called system.  If the called system
is a xenix system, it will start the remote uucico with the debug flag,
and the remote system will mix the diagnostics with the uucp handshake
and such.

Horrible confusion is a result, which is why I like the helpful diag msg
in the remote (xenix) system's logfile:
uucp xsys (mm/dd-hh:mm) CAUGHT (SIGNAL 1)
Where "uucp" = uucp login, "xsys" = name of xenix system, and
date-time are within the parens.

This is particularly pernicious, because it appears when you most need
for things to work right:  when you are setting up and testing a
connection for the first time!

Fix:
Determine whether any system to which you are about to establish a
link is a xenix system.  If you are a xenix system to which someone is
trying to establish a link, warn them.  If uucico is invoked without
the debugging (no -Xn), it works OK.

If this problem has appeared elsewhere, I would be interested in hearing
of it by mail please.
-- 
<std dsclm, copies upon request>	   Tanner Andrews, KI4PV
uucp:					...!decvax!ucf-cs!ki4pv!tanner