Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO Unix 3.2.2 ksh seems to hang mmdf->uucp connection
Message-ID: <1991Jun19.053715.7011@kithrup.COM>
Date: 19 Jun 91 05:37:15 GMT
References: <1991Jun18.235817.3784@shograf.com>
Organization: Kithrup Enterprises, Ltd.
Lines: 29

In article <1991Jun18.235817.3784@shograf.com> jim@shograf.COM (jim morris) writes:
>On a SCO Unix SYSvR3.2
>Has anyone else noticed this problem?? I am trying to localize it.

Yes, and it's been talked about before.

ksh is not causing the problem.  Well, not directly.  What's happening, as
near as I could figure out, is that cu is doing something to the tty device
when it sees any one of a few special characters (intr, eof, or a couple
others, I think).  It's either closing and then reopening, or doing an
ioctl; I don't recall which.  In any event, if you have job control "turned
on" (via a 'set -m', which is automatic in an interactive ksh), the second
cu process gets a SIGTTOU (I believe), and ... stops.

Work around:  do

	set +m ; cu <...> ; set -m

If you have paid SCO for support, call them up and ask if they've got
anything to fix it.  It was common enough that they may have.  (I kinda
cheated... I didn't feel like delving through the source, so I just put in
some signal(SIG_IGN, signo); calls...  Not the proper thing to do, I know,
but it let me do what I wanted to do.)

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef@kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.