Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: SIGINT handling
Date: Mon, 21 Sep 2015 17:04:12 +0100
Lines: 21
Approved: bug-bash@gnu.org
Message-ID: <mailman.1545.1442851465.19560.bug-bash@gnu.org>
References: <20150918151439.GA16455@chaz.gmail.com> <20150919203628.GA27872@chaz.gmail.com> <20150921094807.GA6229@chaz.gmail.com> <20150921153536.GA91724@stack.nl>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: bug-bash <bug-bash@gnu.org>
To: Jilles Tjoelker <jilles@stack.nl>
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <20150921153536.GA91724@stack.nl>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: list
Xref: csiph.com gnu.bash.bug:11525

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