[haiku-development] Re: Bash and Jobs
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 29 Aug 2007 14:17:06 +0200
On 2007-08-29 at 13:47:23 [+0200], François Revol <revol@xxxxxxx> wrote:
> > Interestingly, when the shell is "exit"ed, jobs will only be sent a
> > SIGHUP,
> > if that had explicitly been specified before (via "shopt -s
> > huponexit").
> > That is normally all jobs will continue to enjoy their good health
> > even
> > after the terminal has gone.
> >
> > Personally I find this more than a bit inconsistent and wonder, if we
> > want
> > to change that behavior. Any opinions?
> >
>
> The user might think closing the window is the correct way, but to the
> shell it's a horrible death, and not the correct way to exit it. It's
> not the same, and those using the shell shall know that.
> Also sometimes one starts a terminal to [re]start a gui app, and it's
> always a shame to discover closing that terminal killed the gui app you
> just started :)
>
> Now you can always put that shopt command somewhere in /etc/profile or
> bashrc or whatever.
Nope, it affects only the exit behavior (i.e. will then send SIGHUP on exit
as well). Bash's SIGHUP handling can't be influenced by settings.
> Btw, we should upgrade to bash3 someday...
+1 :-)
CU, Ingo
Other related posts:
