From owner-freebsd-questions Mon Jul 28 19:49:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28291 for questions-outgoing; Mon, 28 Jul 1997 19:49:52 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts8-line13.uoregon.edu [128.223.150.77]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28283 for ; Mon, 28 Jul 1997 19:49:49 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id TAA07270; Mon, 28 Jul 1997 19:49:40 -0700 (PDT) Date: Mon, 28 Jul 1997 19:49:40 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Mike Jeays cc: questions@FreeBSD.ORG Subject: Re: Crashed X-server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 28 Jul 1997, Mike Jeays wrote: > Last night I managed to crash my X-server, by attempting to run Xpaint on > a largish JPG file. Rather than driving in to work to telnet in and kill > the server, I pressed the reset button, and kept my fingers crossed. It > repaired the file system automatically, and everything seems to work so > far - but I noticed that the "/" file system seems to be much more full > than I remember, and the the result of an "ls -l /stand" looks peculiar - > although I am not sure if it was always this way. Any clues, please? I don't know about /, you may have some leftovers in /tmp. For /stand, your listing is correct -- it's a crunched hardlined binary (see the link count in the second column). Also, you can use Cntl-Alt-Backspace to kill the X server, or hit Cntl-Alt-F1 to get your console back. Then kill xdm or X and you should be OK. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo