Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!newsfeed.ksu.ksu.edu!news.physics.uiowa.edu!math.ohio-state.edu!cs.utexas.edu!swrinde!tank.news.pipex.net!pipex!dispatch.news.demon.net!demon!longacre.demon.co.uk From: searle@longacre.demon.co.uk (Michael Searle) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Signal 11 Date: Sat, 25 May 1996 17:08:41 BST Lines: 21 Message-ID: <nD3E85F90@longacre.demon.co.uk> References: <nD356D43A@longacre.demon.co.uk> <4o5bp9$gel@jraynard.demon.co.uk> NNTP-Posting-Host: longacre.demon.co.uk X-NNTP-Posting-Host: longacre.demon.co.uk X-Newsreader: Offlite 0.09 / Termite Internet for Acorn RISC OS james@jraynard.demon.co.uk (James Raynard) wrote: > > In article <nD356D43A@longacre.demon.co.uk>, Michael Searle > <searle@longacre.demon.co.uk> wrote: >> Does processes exiting on signal 11 always mean bad hardware (probably >> memory or mainboard), or can they be caused by other things (like buggy >> executables)? > They can also be caused by running out of swap, which certainly sounds > like a possible explanation for the problems you described. How much > swap do you have? 64 megs. Once the signal 11 was when I ran out of swap, but not the other times - with only 16 megs of RAM, it usually becomes too slow to use before I get near using all the swap. -- Michael Searle - searle@longacre.demon.co.uk