[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in force_interactive handling

From: Stas Sergeev
Subject: Re: bug in force_interactive handling
Date: Mon, 02 Jan 2012 23:10:29 +0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0

02.01.2012 22:53, Chet Ramey wrote:
the script, leaving the process alive.
The SIGSTOP/SIGCONT works to put the process into the background: the
jobs pgrp is not the same as the terminal's pgrp.  If you don't want
the shell to terminate the job at exit because it's stopped, use
`disown' after the job stops to have the shell forget it while you
continue it from another process.
Thanks! The disown might do the trick.

Will your suggestion about the trap handler work
also for ^Z+bg rather than just fg?
It should.
I tried:
trap bg USR1
Now if I first send SIGSTOP to the job and then SIGUSR1 to
bash, that works.
Is it possible to avoid sending SIGSTOP to the job, and make
the trap handler to do both things at once? Not that it is strictly
required since you already described a few other ways, but I wonder. :)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]