From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Peter Stephenson <pws@csr.com>, zsh-workers@sunsite.dk
Subject: Re: GNU nohup oddness
Date: Thu, 12 Dec 2002 04:09:02 +0000 [thread overview]
Message-ID: <1021212040902.ZM23331@candle.brasslantern.com> (raw)
In-Reply-To: <23159.1039456820@csr.com>
On Dec 9, 6:00pm, Peter Stephenson wrote:
} Subject: Re: GNU nohup oddness
}
} "Bart Schaefer" wrote:
} > @@ -870,7 +897,8 @@
} > signal_ignore(SIGQUIT);
} > #endif
} >
} > - install_handler(SIGHUP);
} > + if (signal_ignore(SIGHUP) != SIG_IGN)
} > + install_handler(SIGHUP);
} > install_handler(SIGCHLD);
} > #ifdef SIGWINCH
} > install_handler(SIGWINCH);
}
} Seems to be logical --- follow the parent process.
}
} Is there a place where also setting opts[HUP] to zero would change the
} effect?
With signal_ignore(SIGHUP) any jobs started by that zsh _probably_ will
also ignore HUP -- but without opts[HUP] = 0, zsh still kill()s all jobs
at exit. So with the patch above, background jobs _may_ die when the
script exits, even if the nohup wrapper was used to start the script.
Conversely, if opts[HUP] = 0, then zsh won't kill() even if the script
later un-ignores HUP by installing a trap handler, so background jobs
started by the script will survive even if the script itself is HUP'd.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2002-12-12 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 0:30 Clint Adams
2002-12-06 10:14 ` Bart Schaefer
2002-12-07 15:24 ` Clint Adams
2002-12-07 17:43 ` Bart Schaefer
2002-12-09 18:00 ` Peter Stephenson
2002-12-12 4:09 ` Bart Schaefer [this message]
2002-12-12 10:39 ` Peter Stephenson
2002-12-12 15:33 ` 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=1021212040902.ZM23331@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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).