From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1611 invoked from network); 22 Feb 2003 22:04:46 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 22 Feb 2003 22:04:46 -0000 Received: (qmail 5458 invoked by alias); 22 Feb 2003 22:04:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 18272 Received: (qmail 5445 invoked from network); 22 Feb 2003 22:04:31 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 22 Feb 2003 22:04:31 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [4.64.233.231] by sunsite.dk (MessageWall 1.0.8) with SMTP; 22 Feb 2003 22:4:30 -0000 Received: (from schaefer@localhost) by candle.brasslantern.com (8.11.6/8.11.6) id h1MN4G410266 for zsh-workers@sunsite.dk; Sat, 22 Feb 2003 15:04:16 -0800 From: "Bart Schaefer" Message-Id: <1030222230416.ZM10265@candle.brasslantern.com> Date: Sat, 22 Feb 2003 23:04:16 +0000 In-Reply-To: <200302211807.h1LI74n23531@aragorn.cortexmachina.com> Comments: In reply to Peter Whaite "Cant fg a suspended su (4.1.0-dev-7)" (Feb 21, 1:07pm) References: <200302211807.h1LI74n23531@aragorn.cortexmachina.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.dk Subject: Re: Cant fg a suspended su (4.1.0-dev-7) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Feb 21, 1:07pm, Peter Whaite wrote: } } I've noticed that I cannot resume a suspened su session lately (It } happened in 4.1.0-dev-6 as well). } } There is approximately a 1 second pause between the contined and the } suspended messages. } } Any idea why the su command re-suspends after the continue? It appears to be this loop in bin_suspend(): 1669 if (jobbing) { 1670 /* stay suspended */ 1671 while (gettygrp() != mypgrp) { 1672 sleep(1); 1673 if (gettygrp() != mypgrp) 1674 kill(0, SIGTTIN); 1675 } 1676 /* restore signal handling */ 1677 signal_ignore(SIGTTOU); 1678 signal_ignore(SIGTSTP); 1679 signal_ignore(SIGTTIN); 1680 } However, that code has been there forever [*] so the actual problem must lie in some change that's been made to tty process group handling. I would tend to suspect that zsh-workers/17859 is the culprit. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net