From owner-freebsd-current@FreeBSD.ORG Tue Apr 17 19:41:00 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99DF91065675 for ; Tue, 17 Apr 2012 19:41:00 +0000 (UTC) (envelope-from jasone@freebsd.org) Received: from canonware.com (10140.x.rootbsd.net [204.109.63.53]) by mx1.freebsd.org (Postfix) with ESMTP id 777B08FC17 for ; Tue, 17 Apr 2012 19:41:00 +0000 (UTC) Received: from [172.25.16.174] (unknown [173.252.71.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by canonware.com (Postfix) with ESMTPSA id CB8E428419; Tue, 17 Apr 2012 12:40:59 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=utf-8 From: Jason Evans In-Reply-To: Date: Tue, 17 Apr 2012 12:40:59 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <24C092D6-E322-49DD-A895-0E3A588DF654@freebsd.org> References: <4F8D2CE5.2030106@mail.zedat.fu-berlin.de> <20120417155140.12dfe277@nonamehost.> <4F8D68DF.9040101@mail.zedat.fu-berlin.de> To: John Nielsen X-Mailer: Apple Mail (2.1257) Cc: freebsd-current@freebsd.org Subject: Re: : Conf string ends with key X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 19:41:00 -0000 On Apr 17, 2012, at 12:10 PM, John Nielsen wrote: > On Apr 17, 2012, at 8:58 AM, O. Hartmann wrote: >> On 04/17/12 14:51, Ivan Klymenko wrote: >>> =D0=92 Tue, 17 Apr 2012 10:42:13 +0200 >>> "O. Hartmann" =D0=BF=D0=B8=D1=88=D0= =B5=D1=82: >>>=20 >>> remove /etc/malloc.conf >>=20 >> simple and efficient ;-) >=20 > I encountered this today as well. I set /etc/malloc.conf a long time = ago and haven't thought about it much since. The new options format is = documented in jemalloc(3), but I for one would have appreciated a = heads-up of some sort. Should this be an entry in UPDATING? I just sent a HEADSUP email, and will add an entry to UPDATING. Thanks = for the suggestion. Jason=