[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SIGINT handling
From: |
Stephane Chazelas |
Subject: |
Re: SIGINT handling |
Date: |
Mon, 21 Sep 2015 17:04:12 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
2015-09-21 17:35:36 +0200, Jilles Tjoelker:
[...]
> This kind of job control manipulation is very hard to get right in the
> general case. FreeBSD's su does it, and it needed various iterations to
> fix hanging processes or unexpected logouts, some of which only occur
> when the application is started from certain shells.
>
> Also, it is not possible to fix generally cases like
> su SOMEUSER -c 'while sleep 0.1; do echo @@@; done' | less
> where there are other processes in the same process group as the one
> doing job control manipulations. If su changes the tty's foreground
> process group, it will prevent less from reconfiguring terminal modes.
[...]
What was the rationale for adding that to "su"? I'd have
expected job control to be only done by interactive
applications.
--
Stephane
- SIGINT handling, Stephane Chazelas, 2015/09/18
- Re: SIGINT handling, Stephane Chazelas, 2015/09/19
- Re: SIGINT handling, Stephane Chazelas, 2015/09/21
- Re: SIGINT handling, Chet Ramey, 2015/09/21
- Re: SIGINT handling, Stephane Chazelas, 2015/09/21
- Re: SIGINT handling, Stephane Chazelas, 2015/09/21
- Re: SIGINT handling, Chet Ramey, 2015/09/22
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
- Re: SIGINT handling, Chet Ramey, 2015/09/22
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
Re: SIGINT handling, Chet Ramey, 2015/09/19