Date: Tue, 28 Apr 1998 13:13:44 -0500 (EST) From: "John S. Dyson" <dyson@FreeBSD.ORG> To: dec@phoenix.its.rpi.edu (David E. Cross) Cc: jkh@time.cdrom.com, adrian@virginia.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: SIGDANGER Message-ID: <199804281813.NAA00553@dyson.iquest.net> In-Reply-To: <Pine.BSF.3.96.980428071319.15319A-100000@phoenix.its.rpi.edu> from "David E. Cross" at "Apr 28, 98 07:19:16 am"
next in thread | previous in thread | raw e-mail | index | archive | help
David E. Cross said: > > As per memory overcomitment, I do not see this as an issue, I can still > run out of memory even if I am not over commited (say netscape went > berkerk or whatever). I think thet in situation where the system is > starting to page (or heavily paging) SIGDANER [Will Robinson] would be a > usefull tool. > I used to work where we had customers using SVR4. Those customers had as many (or more) problems with processes being killed or dying unexpectedly, even without overcommit. The startup code for processes in SVR4 dies badly in code supplied by the vendor when swap space is low. It doesn't solve the problem of unintended processes dying unless processes are written correctly. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804281813.NAA00553>