From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3/2) with ESMTP id RAA16689 for ; Mon, 15 Jul 1996 17:01:49 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id CAA09367; Mon, 15 Jul 1996 02:35:43 -0400 (EDT) Resent-Date: Mon, 15 Jul 1996 02:35:43 -0400 (EDT) Message-Id: Date: Mon, 15 Jul 96 08:37 MET DST From: Sven Wischnowsky To: zsh-workers@math.gatech.edu In-reply-to: Zoltan Hidvegi's message of Mon, 15 Jul 1996 04:43:32 +0200 (MET DST) Subject: Re: Blocking child signals Resent-Message-ID: <"Cv1S82.0.HI2.-QUwn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/1651 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu 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