From owner-freebsd-current Tue Aug 13 18:13: 0 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 8A01D37B401 for ; Tue, 13 Aug 2002 18:12:58 -0700 (PDT) Received: from web20909.mail.yahoo.com (web20909.mail.yahoo.com [216.136.226.231]) by mx1.FreeBSD.org (Postfix) with SMTP id 07DD043E3B for ; Tue, 13 Aug 2002 18:12:58 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020814011257.25645.qmail@web20909.mail.yahoo.com> Received: from [218.97.164.167] by web20909.mail.yahoo.com via HTTP; Tue, 13 Aug 2002 18:12:57 PDT Date: Tue, 13 Aug 2002 18:12:57 -0700 (PDT) From: David Xu Subject: Re: cvs commit: src/sys/kern kern_sig.c (fwd) To: Terry Lambert Cc: Tim Robbins , current@FreeBSD.ORG In-Reply-To: <3D599E84.1AF6FEB4@mindspring.com> 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 --- Terry Lambert wrote: > David Xu wrote: > > > 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. > > > > I have very current source, and don't have any problem you have encountered. > > I can not reproduced it. > > > Both different reports have been from Tim Robbins. It may > be that he has a local problem, and that his local problem > is greatly confusing this discussion. > > If you can not repeat his second problem on -current locally, > I would be tempted to dismiss it as being a local problem, and > not a general one. > > Tim was also the person who posted the GPL'ed path that I was > worried that Andrey was using against "su"; not to disparage > anyone, but most of my personal confusion has been coming from > things Tim said... 8-). > > -- Terry My machine may be different with Tim's, it is a P4 1.5G CPU, its speed maybe fast enough to skip the problem. BTW, bde has also reported the problem, so this is serious, wouldn't kernel send out SIGTTOU when null change a foreground group is enough to fix the problem?. but why don't they block SIGTTOU when calling tcsetpgrp()? David __________________________________________________ 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