zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: Vincent Stemen <zsh@hightek.org>,
	zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: (2) Re: FreeBSD compatability feature request
Date: Fri, 23 Apr 2004 10:56:56 +0100	[thread overview]
Message-ID: <16448.1082714216@csr.com> (raw)
In-Reply-To: "Vincent Stemen"'s message of "Fri, 23 Apr 2004 00:30:44 CDT." <20040423053044.GA75851@quark.hightek.org>

Vincent Stemen wrote:
> I also don't have a full understanding of all aspects of signal
> handling, but it looks to me like in order to implement trapsasync
> mode, it would involve using the WNOHANG option to waitpid() or
> wait3() or wait4() to periodically check the child status without
> blocking the parent until the child exits.  That way I am guessing you
> can immediately receive signals in the parent and kill the child,
> exit, or whatever.  My question is, does that affect the child's
> ability to be interactive.

Some parts of the shell do use this, but in the main part where the
shell waits for a job (zwaitjob() in jobs.c) it simple calls
sigsuspend(), installing a particular signal mask.  What's more, there's
already a loop, so it's reasonably safe about bogus signals.  It looks
likes it's probably not too hard to alter, except that signals are tricky
things.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2004-04-23  9:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040417222222.GA27230@quark.hightek.org>
     [not found] ` <21533.1082374109@csr.com>
2004-04-21  8:21   ` Vincent Stemen
2004-04-21 10:00     ` Peter Stephenson
2004-04-21 11:05     ` PATCH: (2) " Peter Stephenson
2004-04-22  8:59       ` Vincent Stemen
2004-04-22  9:59         ` Peter Stephenson
2004-04-22 10:17           ` Peter Stephenson
2004-04-22 16:09             ` Jos Backus
2004-04-23  5:30               ` Vincent Stemen
2004-04-23  9:56                 ` Peter Stephenson [this message]
2004-04-27  3:56             ` Bart Schaefer
2004-04-27  9:58               ` Peter Stephenson
2004-04-29  2:16                 ` Vincent Stemen
2004-04-30 21:26         ` PATCH: (3) " Peter Stephenson
2004-05-01  1:45           ` Vincent Stemen
2004-05-01  2:23             ` Vincent Stemen
2004-05-04  7:17           ` PATCH: (3) - FreeBSD compatability issue resolved Vincent Stemen
2004-05-04  9:28             ` Peter Stephenson

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=16448.1082714216@csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    --cc=zsh@hightek.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).