From owner-freebsd-current Thu Feb 7 12:41:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id C80EE37B400 for ; Thu, 7 Feb 2002 12:41:03 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g17KfO627321; Thu, 7 Feb 2002 12:41:25 -0800 (PST) Date: Thu, 7 Feb 2002 12:41:24 -0800 (PST) From: Doug White To: Jacob Frelinger Cc: current@FreeBSD.ORG Subject: Re: Bizzare problem.. In-Reply-To: <20020206175906.B26239@thecoffinclub.com> Message-ID: <20020207124059.W25743-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us 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 Wed, 6 Feb 2002, Jacob Frelinger wrote: > On Wed, Feb 06, 2002 at 01:08:10PM -0800, Doug White wrote: > > On Tue, 5 Feb 2002, Jacob Frelinger wrote: > > > > You aren't using a Linux version of vi, are you? It so happens a common > > freebsd system call maps to linux reboot() .... > > > > it shouldn't be. > [jolly@spooky ~]# which vi > /usr/bin/vi > [jolly@spooky ~]# strings /usr/bin/vi | head -2 > /usr/libexec/ld-elf.so.1 > FreeBSD > > and that wouldn't explain the shutdowns when i ssh from the problematic > machine into a different one and run vi on the remote machine. > > i wish it was something that simple... i'm completly stumped on this... I think I'd chock it up to bad memory at this point. Teh reboots could be a parity failure and some systems reboot in that condition ... Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message