From owner-freebsd-chat Thu Apr 15 11:34:53 1999 Delivered-To: freebsd-chat@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id ED0F514BD5 for ; Thu, 15 Apr 1999 11:34:50 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA61189; Thu, 15 Apr 1999 14:30:13 -0400 (EDT) Date: Thu, 15 Apr 1999 14:30:13 -0400 (EDT) From: Chuck Robey To: Anthony Kimball Cc: "Daniel C. Sobral" , chat@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <14102.8184.91918.375800@avalon.east> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 15 Apr 1999, Anthony Kimball wrote: > Quoth Daniel C. Sobral on Thu, 15 April: > : > : FreeBSD executes ANSI C code reliably according to spec, as long as > : there is enough memory in the system. If there isn't, FreeBSD > : doesn't run reliably, much less executes any kind of code reliably. > : > I understand this. I concieve the purpose of this thread as being > a clear determination of the best known way to allow correctly > written code to run reliably when, for reasons perhaps out of the > control of the application, memory becomes overcommitted. It might have been that, if on the second line of your original post you didn't claim we were ANSI incompatible. As it was, it sounded much like chicken little yelling the sky was falling. Your position now seems to have changed quite a bit. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message