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!inferno.mpx.com.au!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.uoknor.edu!news.nodak.edu!netnews1.nwnet.net!netnews.nwnet.net!news.u.washington.edu!uw-beaver!uhog.mit.edu!news.mathworks.com!tank.news.pipex.net!pipex!dispatch.news.demon.net!demon!jraynard.demon.co.uk!not-for-mail From: james@jraynard.demon.co.uk (James Raynard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Signal 11 Date: 24 May 1996 22:04:25 -0000 Organization: A FreeBSD Box Lines: 14 Message-ID: <4o5bp9$gel@jraynard.demon.co.uk> References: <nD356D43A@longacre.demon.co.uk> NNTP-Posting-Host: localhost.demon.co.uk X-NNTP-Posting-Host: jraynard.demon.co.uk 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? -- James Raynard, Edinburgh, Scotland jraynard@dial.pipex.com james@jraynard.demon.co.uk