SCO Unix 3.2.2 cu problem: locks up during intr character: solution
Sean Eric Fagan
sef at kithrup.COM
Thu Jan 17 11:40:58 AEST 1991
In article <1483 at beaudin.UUCP> john at 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 at 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.
More information about the Comp.unix.sysv386
mailing list