On 21.11.20 г. 23:15 ч., Chet Ramey wrote:
> On 11/21/20 2:32 PM, Andreas Schwab wrote:
>> On Nov 21 2020, Chet Ramey wrote:
>>
>>> but since the shell always ignores SIGTERM,
>>
>> Even a non-interactive shell?
>
> No, you're right, it's SIGQUIT the shell always ignores. It catches SIGTERM
> i
On 2/3/21 7:54 AM, Nikolay Borisov wrote:
Have you had a chance to look into this?
There is a fix in the devel branch.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://ti
The problem that I have seems much the same as from Feb 2019:
https://www.mail-archive.com/bug-bash@gnu.org/msg22665.html
Try to login on a serial console, see the message:
bash: initialize_job_control: no job control in background: Bad file descriptor
This is what is running:
# ps -ft tty2
On 1/31/21 9:26 PM, Alex fxmbsw7 Ratchev wrote:
( http://ix.io/2NUp ) - sadly i dont have the depaster ready, some loop
deep logic faukts
bash-5.1# n=1 bash paster $( < thefiles )
++ paste BEGIN ++
++ paste BEGINFILE theintro
hello to this bug report, consisted as one big text file of pastes o
On 2/3/21 9:04 AM, Alain D D Williams wrote:
The problem that I have seems much the same as from Feb 2019:
https://www.mail-archive.com/bug-bash@gnu.org/msg22665.html
Yes, it's the same.
Try to login on a serial console, see the message:
bash: initialize_job_control: no job control in back
On Wed, Feb 03, 2021 at 12:07:38PM -0500, Chet Ramey wrote:
> So your shell is not running in the same process group as the terminal,
> and has no access to read from its controlling terminal.
Thanks ... you gave me a clue to fix this. Not ideal, but it works.
if [[ -n $SHELL && -z $SSH_AGENT_PID
On 2/3/21 4:46 PM, Kevin Buchs wrote:
Ok, if that restriction is not going to be lifted, then the documentation
should reflect it.
The documentation does reflect that job control cannot be active:
lastpipe
If set, and job control is not active, the shell runs
