Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!csun!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO Unix 3.2.2 cu problem: locks up during intr character: solution
Message-ID: <1991Jan17.004058.5345@kithrup.COM>
Date: 17 Jan 91 00:40:58 GMT
References: <1483@beaudin.UUCP>
Organization: Kithrup Enterprises, Ltd.
Lines: 18

In article <1483@beaudin.UUCP> john@beaudin.UUCP (John Beaudin) writes:
>It was ksh's job control which was interfering. SCO's solution was 

Uhm, ksh doesn't have job control.  It *supports* it, but it's the kernel
which has job control.

The solution you gave only masks the symptom; the problem is that cu is
being set SIGTTOU when it tries to write, after noticing any one of a few
special characters:  intr, eof, and kill, I believe.

So, yes, doing a 'set +m' will solve it, for ksh.  But that has its own
problems, as well.

-- 
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.