From owner-freebsd-current Tue Sep 10 17:04:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA25221 for current-outgoing; Tue, 10 Sep 1996 17:04:55 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA25216 for ; Tue, 10 Sep 1996 17:04:53 -0700 (PDT) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id RAA13005; Tue, 10 Sep 1996 17:05:33 -0700 Date: Tue, 10 Sep 1996 17:05:31 -0700 (PDT) From: Veggy Vinny To: Chuck Robey cc: FreeBSD current Subject: Re: sh In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 10 Sep 1996, Chuck Robey wrote: > Am I the only one who is starting to get strange reactions out of my sh? > I'm starting to get those signal-11's, and for once I hope my sh (I > noticed the recent changes) is broken in some way. The signal 11's are > coming too incredibly predictably for it to be a memory fault alone. It's not just you but on one of our machines, mercury.gaianet.net, it seems like after the last reboot... it said can't execute /bin/sh, any ideas how to fix this? Since I can't do it remotely, I need to explain it to the guy by email... Vince