zsh-workers
 help / color / mirror / code / Atom feed
From: Alan Pinstein <apinstein@me.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Commands run from functions don't exit cleanly on terminal close (SIGHUP)?
Date: Thu, 25 Oct 2012 07:48:30 -0400	[thread overview]
Message-ID: <D1AA5CA1-BB91-45D4-90D7-1596FF81F6AE@me.com> (raw)
In-Reply-To: <20121025112222.3dfbb213@pws-pc.ntlworld.com>

I didn't even think about it being platform dependent. I am on Mac OS 10.7.5. I will try to test on a centos box today. 

Alan

On Oct 25, 2012, at 6:22 AM, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:

> On Wed, 24 Oct 2012 10:10:42 -0400
> Alan Pinstein <apinstein@mac.com> wrote:
>> I need to make one clarification; the PPID ends up as 1 (orphaned) if
>> no traps are installed; if the HUP trap is installed, the PPID remains
>> correct, but it still doesn't exit.
> 
> In my case (Fedora 15 on x86_64), I'm seeing the programme exit if there
> aren't any traps, so I've got different behaviour.  This could be as the
> result of a race or indeed pretty much anything else...
> 
> With the HUP trap, it's not exiting, but that doesn't actually surprise
> me:  you're handling the trap within the shell, so it's not being
> propagated as a signal to PHP.
> 
> There are lots of variables, I'll try to experiment some more, in
> particular finding differences between the behaviour in functions and
> not (which wouldn't surprise me, there is some special handling).
> 
> pws


  reply	other threads:[~2012-10-25 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 14:03 Alan Pinstein
2012-10-24 14:10 ` Alan Pinstein
2012-10-25 10:22   ` Peter Stephenson
2012-10-25 11:48     ` Alan Pinstein [this message]
2012-10-25 13:22       ` Alan Pinstein
2012-10-25 14:03         ` Peter Stephenson
2012-10-25 14:54         ` Bart Schaefer

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=D1AA5CA1-BB91-45D4-90D7-1596FF81F6AE@me.com \
    --to=apinstein@me.com \
    --cc=zsh-workers@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).