Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: 3.0.6-pre-5 problem
- X-seq: zsh-workers 6861
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: 3.0.6-pre-5 problem
- Date: Fri, 25 Jun 1999 16:29:19 +0000
- In-reply-to: <199906251252.OAA02488@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199906251252.OAA02488@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Jun 25, 2:52pm, Sven Wischnowsky wrote:
} Subject: Re: 3.0.6-pre-5 problem
}
} I could finally reproduce it when trying to look at it with strace,
} which finally opened my eyes (I would have needed a `ps j' output).
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
5161 5162 5162 5162 p4 5162 T 674 0:00 Src/zsh -f
5162 5164 5162 5162 p4 5162 T 674 0:00 mutt
28198 5165 5165 28198 p3 5165 R 674 0:00 ps j
28198 5161 5161 28198 p3 5169 S 0 0:00 xterm -e Src/zsh -f
zsh(28198)-+-pstree(5173)
`-xterm(5161)---zsh(5162)---mutt(5164)
} It goes like this: Someone exec()s zsh without putting it into its own
} process group. Then we start the function and zsh executes external
} commands in its own process group.
The top-level xterm case is now producing process trees exactly like
the case where there's an intermediate zsh, but the parent zsh is still
not ignoring the TSTP.
} So, if we have agreed to use the kill-loop-patches, we'll have to make
} sure that every decent interactive zsh with job-control runs in its
} own process group which is what the patch below does.
This is a good idea in any case.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author