From owner-freebsd-current Thu Jun 6 19:44:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA15302 for current-outgoing; Thu, 6 Jun 1996 19:44:33 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA15271 for ; Thu, 6 Jun 1996 19:44:25 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id aa20822; 7 Jun 96 2:50 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa11409; 7 Jun 96 2:50 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id CAA02611; Fri, 7 Jun 1996 02:03:44 GMT Date: Fri, 7 Jun 1996 02:03:44 GMT Message-Id: <199606070203.CAA02611@jraynard.demon.co.uk> From: James Raynard To: plm@xs4all.nl CC: freebsd-current@freebsd.org In-reply-to: <199606060533.HAA02276@plm.xs4all.nl> (message from Peter Mutsaers on Thu, 6 Jun 1996 07:33:10 +0200 (MET DST)) Subject: Re: More on VM, swap leaks Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > JH> Another possibility is a bad emacs binary. Especially since > JH> as part of the compilation process, emacs runs itself, loads > JH> in a bunch of LISP, then pukes itself out as a new executable. > JH> I shudder to think what could happen if a buggy kernel or bad > JH> SIMM decided to rear its head at that point. > > I have the same problems. I have had other programs die, as well Emacs:- Jun 4 16:05:00 jraynard /kernel: pid 10265 (atrun), uid 0: exited on signal 10 Jun 6 23:16:05 jraynard /kernel: pid 148 (innd), uid 8: exited on signal 10 -- James Raynard, Edinburgh, Scotland | http://freefall.freebsd.org/~jraynard/ james@jraynard.demon.co.uk | jraynard@freebsd.org