Re: zsh bug-hang on startup after exec

[Ryan Richter <bobort@abacus.dorm.reed.edu>]

On 22-Mar-2001 Bart Schaefer wrote:
> Why zsh is not becoming the process group leader, I don't know.  Obviously
> bash must be exec'ing it before making *itself* the process group leader,
> but then who *is* the group leader, a?
> 
> Note that
> 
> getpid()                                = 20122
> getpgrp()                               = 20120
> ioctl(10, TIOCGPGRP, [20121])           = 0
> 
> So there are at least three processes involved here ... the process group
> leader is 20120 (whatever that was), but the tty group leader is 20121,
> and neither of those is zsh (20122), so (mypgrp == mypid) is never going
> to be true.

I ran it again by doing 'su myself -c bash', and the process group leader is
su and the tty group leader is strace, which would originally have been bash. 

Did it again with bash just execing zsh and attached strace after zsh started. 
In this case the process group leader is su and the tty group leader is zsh.

> } Anyway, this is a linux 2.2.19 i686 system with glibc 2.1.3, and zsh was
> } compiled with egcs 1.1.2.
> 
> Why does everyone always identify their Linux system by kernel version and
> glibc version?  That's almost never enough information.  The vendor (e.g.
> redhat) and vendor's version number (e.g. 7.1) are almost always much more
> useful.  In this case it'd also be nice to know how you're logging in; is
> it on the text console?  Remote shell?  XDM console?  If the latter, are
> you using vanilla XDM, KDE, Gnome, or something else?

Well, this system started off as redhat 5.1, but it's probably best
approximated by redhat 6.2 at present.  I was logging in via the console and
with su.  I just tried logging in remotely via ssh and it didn't hang.
-- 
Ryan