From: lampman@fullfeed.fullfeed.com (Ray Lampman)
Newsgroups: comp.sys.sun.admin,comp.os.coherent
Subject: Re: UUCP problems w/Sun (solution for likely cause)
Summary: Use "P_ZERO" pseudo-string in chat script to change transmitting parity.
Keywords: sun uucp coherent
Date: 29 Dec 92 18:52:19 GMT
Expires: Tue, 29 Jun 1993 07:11:14 GMT
Reply-To: Ray.Lampman@FullFeed.Com
Followup-To: comp.sys.sun.admin
Organization: FullFeed - Public Access Usenet/E-mail (+1 608 246 2701 guest)

_________________________________________________________________

This  same  problem  was  discussed  recently  (and  solved)   in
comp.mail.uucp,  comp.sys.sun.admin,  and comp.sys.sun.misc under
the subject "Weird! Sun can't UUCP to other  Sun  except  without
password?" I'll repost the final summary below after a quote.
_________________________________________________________________

In article <1992Dec24.195612.20925@jpradley.jpr.com> filip@jpradley.jpr.com (David Filip) writes:
#
# The problem is that (running uucico manually with -x9) the modem dials
# properly and my chat script seems to work properly (up to and including
# sending the password), however after that the last thing that uucico
# prints is 'imsg>' and then it just sits there until the system I am calling
# times out, hangs up the line, and I see a few garbage characters and a
# DISCONNECTED message from the modem.
#
# The master is a Sun Sparc 1 running Sun OS 4.1.1, and is calling a Coherent
# system running 4.0. The modem on the Sparc is a Telebit Trailblazer.
#
# The Coherent system does not even see the Sparc login (zero bytes in the
# uucico log file), so the connection is obviously not being established.
# On the other hand, I am not sure what the Sparc is waiting for (what does
# imsg> mean ?). Also, the login that I am using into the Coherent system is
# used by other systems, so I don't believe there is a fundamental flaw in
# the setup of the Coherent side.
_________________________________________________________________

>Newsgroups: comp.mail.uucp,comp.sys.sun.admin,comp.sys.sun.misc
>From: lampman@fullfeed.fullfeed.com (Ray Lampman)
>Subject: SUMMARY: Weird! Sun can't UUCP to other Sun except without password?
>Message-ID: <1992Dec24.062950.23125@fullfeed.fullfeed.com>
>Keywords: UUCP parity weird password problem
>Date: Thu, 24 Dec 1992 06:29:50 GMT
_________________________________________________________________

The mystery is solved, thanks to all the people who replied.

   dem@meaddata.com (David Myers)
   "Drew Derbyshire" <ahd@kew.com>
   terry@zoe.network23.com (Terry)
   martini@heaven7.in-berlin.de (Martin P. Ibert)
   pete@tecc.co.uk
   brian@igc.apc.org (Brian J. Coan)
_________________________________________________________________

In article <1992Dec10.192406.13795@fullfeed.fullfeed.com> I wrote:
#
# When the two SunOS 4.1.1 machines are configured so  no  password
# is  needed  on  the UUCP-login, every thing works just great! The
# two uucico processes start  talking  and  files  are  transferred
# across the telephone/modem connection.
#
# However, when a password is installed, the calling Sun sends  the
# password, and the connection is dropped. The calling machine logs
# a bunch of "imsg<" strings and eventually gives up. The answering
# machine  shows  no indication of a successful login. Though getty
# does start a valid "login -p <username>" process.
#
# I've heard rumors that SunOS uses a different parity when sending
# or  receiving  a password. How can I configure one or both of the
# machines to handle password transmission, so  the  other  machine
# will  understand?  If these rumors are not true, does anyone know
# what's going on here? I'm totally baffled, help!!
_________________________________________________________________

I needed to transmit the password using a non-default parity set-
ting.  I  learned  my  uucico  process  understands  a variety of
pseudo-strings which can be included in  the  chat  scripts.  The
special  strings  cause uucico to change the configuration of the
transmitting serial device. My chat script now uses the  "P_ZERO"
string. I ended up with a chat script which looks like this:

   host time device speed phone "" \d in: foo word: P_ZERO "" bar

I learned that all pseudo-strings  must  be  "stand-alone"  send-
them  strings. This usually requires an associated expect-nothing
string (""). In the chat script above, the "P_ZERO" string is in-
terpreted  by uucico causing it to change the transmitting parity
before the password (bar) is sent.
_________________________________________________________________

Thanks again to everyone who helped.

Ray.Lampman
System.Operator
FullFeed.Communications
-- 
Ray.Lampman@FullFeed.Com ,^-_  FullFeed provides public access to
FullFeed Communications  L   `; Usenet news and E-mail, plus UUCP
Madison, WI 53704, USA   \ . J    connections to the Madison area
voice +1 608 246 4239     L__]   data +1 608 246 2701 login guest
Xref: sparky comp.sys.sun.admin:9631 comp.sys.sun.hardware:6423