From owner-freebsd-fs Fri Jul 12 17:29:30 1996 Return-Path: owner-fs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26864 for fs-outgoing; Fri, 12 Jul 1996 17:29:30 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA26838; Fri, 12 Jul 1996 17:28:07 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id AAA07477; Sat, 13 Jul 1996 00:27:59 GMT From: Adam David Message-Id: <199607130027.AAA07477@veda.is> Subject: strangest weirdness To: freebsd-current@freebsd.org Date: Sat, 13 Jul 1996 00:27:54 +0000 (GMT) Cc: freebsd-fs@freebsd.org X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well I have just seen what seems to be an unusual filesystem glitch. I was doing 'make depend' in 2 kernel directories concurrently, and at the same time as another kernel 'make all' was getting towards the end of its processing. Both instances of 'make depend' broke by invoking the editor 'ex' on an empty temporary file, following the first invocation of 'mkdep'. No other instances of 'ex' were running at the time as far as I can tell. This was with an NFS /usr, and I believe that the 'make' executable was reinstalled after the 'make all' was started but before the 'make depend' was started. (yes, it's called stress testing. ;) I have also noticed that executables dump core often on client machines when the files on the fileserver have been updated "under their feet". Okay I know "if it hurts, don't do that", but why do these glitches occur? -- Adam David