zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@adler>
To: zsh-workers@math.gatech.edu
Subject: Re:  Blocking child signals
Date: Mon, 15 Jul 96 08:37 MET DST	[thread overview]
Message-ID: <m0ufhHP-0003wOC@adler.informatik.hu-berlin.de> (raw)
In-Reply-To: Zoltan Hidvegi's message of Mon, 15 Jul 1996 04:43:32 +0200 (MET DST)


Zoltan Hidvegi  wrote:

> 
> In exec.c and in jobs.c there are several child_block() and child_unblock()
> calls.  Tracing the system calls used by zsh it turns out that perhaps the
> majority of these are these child block/unblock calls.  I think that the
> performance of zsh could be improved a little bit by calling these blocking
> code more carefully.  Unfortunately this child blocking stuff is quite a
> mess.  I'm sure that there are some bugs hiding here (ie. the child signal
> may remain blocked sometimes for quite a long time or it may be unblocked
> when it should not be unblocked).
> 

Didn't Richard clean this up relatively recently?

> I think that zsh should not block child signals when it does not fork.  Is
> there anyone who knows the details of this child blocking staff in exec.c?
> Perhaps Sven would know that, but unfortunately it seems that he no longer
> works on zsh :-(. 

I didn't do much with the block/unblock code.

> Btw. does anyone know the current E-mail address of
> Sven?  I'd like to add it to the CONTRIBUTORS file.
> 

Yes, I know it... :-)

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de



             reply	other threads:[~1996-07-15  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-15  6:37 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-07-15  2:43 Zoltan Hidvegi
1996-07-15  6:02 ` Bart Schaefer
1996-07-19  1:08   ` Zoltan Hidvegi

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=m0ufhHP-0003wOC@adler.informatik.hu-berlin.de \
    --to=wischnow@adler \
    --cc=zsh-workers@math.gatech.edu \
    /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).