From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: zsh-users@zsh.org
Subject: Re: How to trap EXIT like in bash
Date: Sat, 4 Apr 2015 22:45:30 +0200 [thread overview]
Message-ID: <mfpihj$vea$1@ger.gmane.org> (raw)
In-Reply-To: <150404114859.ZM14898@torch.brasslantern.com>
* Bart Schaefer (Sat, 4 Apr 2015 11:48:59 -0700)
>
> On Apr 4, 7:43pm, Thorsten Kampe wrote:
> }
> } elif [[ $shell = zsh ]]
> } then
> } trap "echo trapped; exit" INT HUP TERM
> } fi
> }
> } Then Zsh does actually ignore the kill (TERM) signal.
>
> It doesn't ignore the signal, but it may not run the trap either. You
> need the trap on EXIT in there:
>
> trap "echo trapped; exit" EXIT INT HUP TERM
>
> That's because it matters whether the shell itself gets the signal, or
> an external job that's been run *by* the shell gets the signal.
>
> E.g. if I run a script that executes "sleep" and kill the sleep, the
> TERM trap is not run but the EXIT trap will be. If I kill the shell
> itself, the TERM trap is run but the EXIT trap is not.
It gets even weirder: neither `kill -HUP`, nor `kill -INT` nor `kill
-TERM` with the PID of the shell have any influence on the script if
these signals are trapped. What does have an influence is a Ctrl-C
and `kill -KILL`.
The kill commands (except `kill -INT`) work immediately with bash
running the script.
Thorsten
next prev parent reply other threads:[~2015-04-04 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 15:20 Thorsten Kampe
2015-04-04 17:08 ` Philippe Troin
2015-04-04 17:43 ` Thorsten Kampe
2015-04-04 18:20 ` Philippe Troin
2015-04-04 18:48 ` Bart Schaefer
2015-04-04 19:59 ` Thorsten Kampe
2015-04-04 20:25 ` Bart Schaefer
2015-04-04 20:55 ` Bart Schaefer
2015-04-04 21:25 ` Bart Schaefer
2015-04-10 16:28 ` Peter Stephenson
2015-04-10 21:16 ` Bart Schaefer
2015-04-04 21:06 ` Thorsten Kampe
2015-04-04 20:45 ` Thorsten Kampe [this message]
2015-04-04 20:52 ` Bart Schaefer
2015-04-04 18:35 ` Bart Schaefer
2015-04-04 19:41 ` Thorsten Kampe
2015-04-07 7:44 ` Han Pingtian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mfpihj$vea$1@ger.gmane.org' \
--to=thorsten@thorstenkampe.de \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).