From owner-freebsd-current Wed Jun 13 2:58:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B3AE737B409; Wed, 13 Jun 2001 02:58:31 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA16827; Wed, 13 Jun 2001 19:58:08 +1000 Date: Wed, 13 Jun 2001 19:55:55 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Valentin Nechayev Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Terminal line discipline is broken [sorta] In-Reply-To: <20010610145322.A461@iv.nn.kiev.ua> Message-ID: 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 On Sun, 10 Jun 2001, Valentin Nechayev wrote: > Thu, Jun 07, 2001 at 12:04:10, bde (Bruce Evans) wrote about "Re: Terminal line discipline is broken [sorta]": > > > This may be a bug in tcsh. > > Do you really think that shell should not modify signal handling policy > which he obtained as legacy from login? And application which resets > them to appropriate position is buggy? Non-interactive shells certainly shouldn't unblock/unignore blocked/ignored signals. I think it doesn't matter much for interactive shells. Login would only change the system defaults if it is broken. > My ktracing of bash (2.04) shows that it isn't really set procmask > to own values, but uses legacy value. Maybe I'm wrong, but this seems > that sh & bash are buggy, not tcsh. Bash does much more initialization for signals than sh. Maybe it knows what it is doing :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message