From owner-freebsd-stable@FreeBSD.ORG  Thu Oct  8 06:23:28 2009
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8FA3F106568D
	for <freebsd-stable@freebsd.org>; Thu,  8 Oct 2009 06:23:28 +0000 (UTC)
	(envelope-from lehmann@ans-netz.de)
Received: from avocado.salatschuessel.net (avocado.salatschuessel.net
	[78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id D01CB8FC14
	for <freebsd-stable@freebsd.org>; Thu,  8 Oct 2009 06:23:27 +0000 (UTC)
Received: (qmail 11721 invoked by uid 89); 8 Oct 2009 06:23:26 -0000
Message-ID: <20091008062326.11720.qmail@avocado.salatschuessel.net>
References: <20091007200959.3c93904f.lehmann@ans-netz.de>
	<alpine.BSF.2.00.0910071451030.25972@qvzrafvba.5c.ybpny>
In-Reply-To: <alpine.BSF.2.00.0910071451030.25972@qvzrafvba.5c.ybpny>
From: "Oliver Lehmann" <lehmann@ans-netz.de>
To: jhell <jhell@DataIX.net>
Date: Thu, 08 Oct 2009 08:23:26 +0200
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject: Re: samba - SIGABRT
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2009 06:23:28 -0000

jhell writes: 

Hi, 


> This was caused by your setting of the following: 
> 
> security.bsd.map_at_zero=0 
> 
> You can reset that value to 1 and you should be alright to operate like 
> normal otherwise you will have to compile samba over again with the above 
> mentioned configure options.

Yeah this caused the problem. I wonder how I could have
find this by myself (google is not counting ;)) I mean,
the Abort message is not very verbose what the problem
is here.