From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
"Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: loop killing
Date: Fri, 25 Jun 1999 20:23:16 +0400 [thread overview]
Message-ID: <002001bebf27$07d01620$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <001d01bebf1b$85f76dc0$21c9ca95@mow.siemens.ru>
>
> The only difference, that I currently can see, is, that when it does not work,
> zsh is session leader:
Well, it does work with csh (that starts programs in seperate program group) and
does not work with ksh (that starts porgrams in it's own program group). It does
work if program is started alone and not as part of loop. Note the difference
(this is ksh, but the same is true for zsh):
This is for while true; zcat; done case:
bor@itsrm2:/tools/src/zsh-3.1.5-pws-23%> ps -jt pts/12
PID PGID SID TTY TIME CMD
9064 9002 9002 pts/12 0:00 zcat
9002 9002 9002 pts/12 0:00 ksh
And this is for the simple zcat case:
bor@itsrm2:/tools/src/zsh-3.1.5-pws-23%> ps -jt pts/12
PID PGID SID TTY TIME CMD
9072 9072 9002 pts/12 0:00 zcat
9002 9002 9002 pts/12 0:00 ksh
In the first case job PGID == SID and ^Z does not work (zcat gets TSTP but
[zk]sh never gets SIGCLD). In the second case job PGID != SID and all works like
a charm
Now, is it my system bug? Any idea?
/andrej
next prev parent reply other threads:[~1999-06-25 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-25 14:21 Sven Wischnowsky
1999-06-25 15:00 ` Andrej Borsenkow
1999-06-25 16:23 ` Andrej Borsenkow [this message]
1999-06-25 16:29 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
1999-06-24 11:55 Sven Wischnowsky
1999-06-24 9:08 Sven Wischnowsky
1999-06-24 9:00 ` Peter Stephenson
1999-06-25 13:21 ` Andrej Borsenkow
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='002001bebf27$07d01620$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).