Date: Wed, 14 Apr 1999 19:48:13 -0700 From: "David Schwartz" <davids@webmaster.com> To: <alk@pobox.com> Cc: <chat@FreeBSD.ORG> Subject: RE: swap-related problems Message-ID: <000401be86ea$67f596d0$021d85d1@whenever.youwant.to> In-Reply-To: <14101.20211.969312.765706@avalon.east>
next in thread | previous in thread | raw e-mail | index | archive | help
: > : You are assuming that malloc is the only overcommit case. I > do not believe > : this is true. I believe that fork can cause an overcommit too. Likewise, > : even simply running multiple copies of the same executable causes an > : overcommit case. > : > : This may solve something, but it's not the general > overcommit problem. > > It solves the ANSI C compliance problem, which is one whose > significance I understand fairly well, although I do not have to deal > with it myself. ANSI C doesn't specify the behaviour of fork. What about running multiple copies of the same executable? DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000401be86ea$67f596d0$021d85d1>