From owner-freebsd-current  Fri Apr 24 14:56:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA08934
          for freebsd-current-outgoing; Fri, 24 Apr 1998 14:56:01 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ziplink.net (relay-0.ziplink.net [206.15.168.49])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08908
          for <current@freebsd.org>; Fri, 24 Apr 1998 14:55:57 -0700 (PDT)
          (envelope-from mi@xxx.video-collage.com)
Received: from xxx.video-collage.com (xxx.video-collage.com [199.232.254.68])
	by ziplink.net (8.8.7/8.8.7) with ESMTP id RAA23859
	for <current@freebsd.org>; Fri, 24 Apr 1998 17:55:54 -0400 (EDT)
Received: (from mi@localhost)
	by xxx.video-collage.com (8.8.8/8.8.7) id RAA14740
	for current@freebsd.org; Fri, 24 Apr 1998 17:54:31 -0400 (EDT)
	(envelope-from mi)
From: Mikhail Teterin <mi@video-collage.com>
Message-Id: <199804242154.RAA14740@xxx.video-collage.com>
Subject: Re: sysctl from Linux (*envy*)
In-Reply-To: <19980424224346.35645@follo.net> from Eivind Eklund at "Apr 24, 98 10:43:46 pm"
To: current@FreeBSD.ORG
Date: Fri, 24 Apr 1998 17:54:30 -0400 (EDT)
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL35 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Eivind Eklund once stated:

=overcommit_memory:
=
=This file contains only one value.

I prefer the value of /etc/malloc.conf link and the corresponding
environment variables.

=This is a useful feature, since programs often malloc() huge amounts of
=memory 'just in case', while they only use a small part of it.

Are not this programs broken? Never ending discussion will follow...

=Leaving this value at 0 will lead to the failure of such a huge
=malloc(), when in fact the system has enough memory for the program to
=run... On the other hand, enabling this feature can cause you to run
=out of memory and thrash the system to death, so large and/or important
=servers will want to set this value to 0.

=This supposedly also handles things like fork() etc. Linux shouldn't
=have any server-directed features FreeBSD doesn't!

This is true!

	-mi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message