Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #11648

Re: Want way to run background processes with SIGINT unignored

From Ian Jackson <ijackson@chiark.greenend.org.uk>
Newsgroups gnu.bash.bug
Subject Re: Want way to run background processes with SIGINT unignored
Date 2015-10-13 15:58 +0100
Message-ID <mailman.234.1444748403.7904.bug-bash@gnu.org> (permalink)
References <22040.2725.561993.552660@chiark.greenend.org.uk> <561951D3.30606@case.edu> <22042.26444.280754.417761@chiark.greenend.org.uk>

Show all headers | View raw


Ian Jackson writes ("Re: Want way to run background processes with SIGINT unignored"):
> Chet Ramey writes ("Re: Want way to run background processes with SIGINT unignored"):
> > This is the behavior that any new option would toggle.  Some name like
> > `async_sig_ignore' or `async_sig_restore' would work.
> 
> Thanks for your attention and your feedback; I'll get back to you with
> a patch.

This patch is nearly ready and I will send it shortly.


While I was working on the docs aspect I noticed an infelicity in the
documentation.  It generally talk about the signal disposition that
the shell `inherits from its parent'.  For example:

  traps caught by the shell are reset to the values inherited from the
  shell's parent, and traps ignored by the shell are ignored

But this is misleading.  The values that the signals are reset to are
those which the parent inherited _at shell invocation_ (ie, at exec).
If the shell is a subshell (produced with `( )' perhaps), it may have
inherited different settings from its _parent_ (ie, the main shell).

I think this wording should be changed throughout to read `inherited
at shell invocation'.  Do you agree ?  Would you welcome a patch along
those lines ?


Thanks,
Ian.

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: Want way to run background processes with SIGINT unignored Ian Jackson <ijackson@chiark.greenend.org.uk> - 2015-10-13 15:58 +0100

csiph-web