From owner-freebsd-arch@FreeBSD.ORG  Sun May 13 09:29:42 2007
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 5171616A403
	for <freebsd-arch@freebsd.org>; Sun, 13 May 2007 09:29:42 +0000 (UTC)
	(envelope-from fjoe@neo.samodelkin.net)
Received: from neo.samodelkin.net (samodelkin.net [195.62.0.66])
	by mx1.freebsd.org (Postfix) with ESMTP id 03ED813C44C
	for <freebsd-arch@freebsd.org>; Sun, 13 May 2007 09:29:41 +0000 (UTC)
	(envelope-from fjoe@neo.samodelkin.net)
Received: by neo.samodelkin.net (Postfix, from userid 1000)
	id A145D171F7; Sun, 13 May 2007 16:09:13 +0700 (NOVST)
Date: Sun, 13 May 2007 16:09:13 +0700
From: Max Khon <fjoe@samodelkin.net>
To: Ivan Voras <ivoras@fer.hr>
Message-ID: <20070513090913.GA70647@samodelkin.net>
References: <20070512153532.GQ21795@elvis.mu.org>
	<63984.1178992555@critter.freebsd.dk> <f25m78$ik$2@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f25m78$ik$2@sea.gmane.org>
User-Agent: Mutt/1.4.2.2i
Cc: freebsd-arch@freebsd.org
Subject: Re: HEADS DOWN
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 May 2007 09:29:42 -0000

Hi!

On Sun, May 13, 2007 at 02:30:29AM +0200, Ivan Voras wrote:

> >> I like how phk malloc has it as an option.
> > 
> > But notice that it is not an option for programs that runs as root
> > or setuid/setgid etc.
> > 
> > Given the hostility of networks, I would support a more hardcore
> > attitude to memory mismanagement these days.
> 
> Just a data point: many people were turned away from FreeBSD because a
> few PHP releases did a double-free or malloc-inside-signal-handler
> calls. Yes, GNU's malloc should have been stricter, but it's not funny
> when your apache crashes with SIGABORT.

That's not a valid argument. PHP developers hate apache2 and threads. So what?

/fjoe