From owner-freebsd-current Tue Aug 13 16:38:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DBCE37B400 for ; Tue, 13 Aug 2002 16:38:15 -0700 (PDT) Received: from web20907.mail.yahoo.com (web20907.mail.yahoo.com [216.136.226.229]) by mx1.FreeBSD.org (Postfix) with SMTP id A58BD43E72 for ; Tue, 13 Aug 2002 16:38:14 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020813233813.77899.qmail@web20907.mail.yahoo.com> Received: from [210.83.128.34] by web20907.mail.yahoo.com via HTTP; Tue, 13 Aug 2002 16:38:13 PDT Date: Tue, 13 Aug 2002 16:38:13 -0700 (PDT) From: David Xu Subject: Re: cvs commit: src/sys/kern kern_sig.c (fwd) To: Tim Robbins Cc: current@FreeBSD.ORG In-Reply-To: <20020813235939.A10212@dilbert.robbins.dropbear.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Tim Robbins wrote: > On Tue, Aug 13, 2002 at 06:14:38AM -0700, David Xu wrote: > > > --- Terry Lambert wrote: > > > I did. It's still an order of operation problem in the kernel > > > during fork(), as Bruce pointed out in a later posting (so me > > > pointing it out here is probably redundant... 8-)). > > > > > > I still think other code is going to have the problem, too, so > > > changing su alone doesn't fix things. Better to not deliver > > > the tty output stopped signal. > > > > > > -- Terry > > > > Don't touch tty code, if you change, you'll break more code, > > current problem is just because su forks a child process and > > want to take over some job control work from shell, it is of > > course not a easy job. the problem does not exist in STABLE > > branch because su does not fork. > > What about chpass, vipw, and the other pw_edit() consumers? vipw > works correctly wrt suspending with ^Z on 4.6-RELEASE, but does not > on -CURRENT. As far as I can see, pw_edit()'s logic has not been changed. > > This is a slightly different case to that of the shell suspending _itself_, > but I think it's similar enough that the solution may be the same. > > > Tim I have very current source, and don't have any problem you have encountered. I can not reproduced it. David Xu __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message