Date: Mon, 21 Jul 1997 09:58:10 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Jan.Vedeler@student.unisg.ch Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problem with 2.2.2 Message-ID: <Pine.BSF.3.96.970721095632.1259E-100000@localhost> In-Reply-To: <C12564D9.00719747.00@puccini.unisg.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Jul 1997 Jan.Vedeler@student.unisg.ch wrote: > I cant locate the problem, but if I f.ex. run MC and try to get info from > the disk (F9 - I) I get the message "pid 507(mc), uid 0: exited on signal > 11 - segmentation fault". Then the system start to act cracy. Where is this? There isn't a system utility called 'mc' as far as I can find, at least in versions < 2.2.2. If it crashes and thus causes the system to crash, perhaps you shouldn't be using it? :) > What I can find in this situation is that the rc.conf-file starts to be > corrupted. It looks like as if all comments in the rc.conf duplicates - > "the file starts to grow" - more or less every time I do something. And at > the end it is finally corrupt - and some strange behavior comes up during > booting. There is also a backup of the rc.conf - rc.conf.previous, but this > will of course also go nuts if this "duplication" has been done 2 times. This sounds like some filesystem corruption. Run fsck -y on all your filesystems to make sure they're clear. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970721095632.1259E-100000>