On Thu, May 31, 2012 at 4:41 PM, Glenn Fowler <[email protected]> wrote: > > sorry for the delay on this > > look at src/cmd/ksh93/tests/pty.sh > the test with this label > L POSIX sh 099(C) > sends ^C on this line > c echo bad\cC > > On Wed, 11 Apr 2012 21:40:46 +0200 =?KOI8-R?B?z8zYx8Egy9LZ1sHOz9fTy8HR?= > wrote: >> Glenn, do you have any example which shows how to use your pty utility >> to send a ctrl-c to a process connected to the terminal managed by >> pty? I like to make a test case for the problem below but I fail to >> make one using pty. > >> Olga > >> ---------- Forwarded message ---------- >> From: David Korn <[email protected]> >> Date: Wed, Apr 11, 2012 at 9:36 PM >> Subject: Re: Re: [ast-users] read -d hangs when reading from <() pipes >> To: [email protected], [email protected], >> [email protected] > >> cc: [email protected] [email protected] >> Subject: Re: Re: [ast-users] read -d hangs when reading from <() pipes >> -------- > >> > But I think the real bug was that ksh -c 'read -d "3" r <(printf >> > "x123hello\n") ; printf "|%s|\n" "$r"' can't be terminated by ^C in an >> > xterm. Can you try that on your machine, please? >> > >> > > >> Yes, the real problem is that ^C doesn't interrupt in this case.
How can I send other signals like SIGKILL or SIGRT to the terminal group managed by the pty command? Irek _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
