john@beaudin.UUCP (John Beaudin) (01/16/91)
It was ksh's job control which was interfering. SCO's solution was $ set +m $ cu $ set -m Indeed, the problem goes away if job control is turned off before running cu. -- My .signature is awaiting apropriate display technology
sef@kithrup.COM (Sean Eric Fagan) (01/17/91)
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.