Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15849
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Protect Loop Execution with Traps |
| Date | 2020-01-29 15:22 -0500 |
| Message-ID | <mailman.64.1580329368.2384.bug-bash@gnu.org> (permalink) |
| References | (4 earlier) <20200128210721.GU1350@eeg.ccf.org> <59.1580277932@jinx.noi.kre.to> <20200129143352.GY1350@eeg.ccf.org> <20200129201907.GA17112@localhost4.local> <20200129202244.GL1350@eeg.ccf.org> |
On Wed, Jan 29, 2020 at 03:19:07PM -0500, Roger wrote:
> >sigint_handler() {
> > trap - INT
> > kill -INT $$
> >}
> >trap sigint_handler INT
>
> One thing to note here, I tried inserting the "trap sigint_handler INT" prior
> to the loop/for/while statement (or outside of the loop) and the trap doesn't
> work as you state it does for yourself.
>
> I find I have to insert "trap sigint_handler INT" within my loop (for/while)
> section of code, for the trap to work. In my eyes or for me, this works as
> expected.
That sounds like your loop is inside a subshell. Possibly because
you're using it in a pipeline, or possibly other reasons.
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Protect Loop Execution with Traps Greg Wooledge <wooledg@eeg.ccf.org> - 2020-01-29 15:22 -0500
csiph-web