Date: Tue, 17 Apr 2012 15:10:49 -0400 From: John Nielsen <lists@jnielsen.net> To: freebsd-current@freebsd.org Cc: Jason Evans <jasone@canonware.com> Subject: Re: <jemalloc>: Conf string ends with key Message-ID: <D1956364-054B-4598-97EB-664D0EDB3B08@jnielsen.net> In-Reply-To: <4F8D68DF.9040101@mail.zedat.fu-berlin.de> References: <4F8D2CE5.2030106@mail.zedat.fu-berlin.de> <20120417155140.12dfe277@nonamehost.> <4F8D68DF.9040101@mail.zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <ohartman@mail.zedat.fu-berlin.de> =D0=BF=D0=B8=D1=88=D0=B5= =D1=82: >>=20 >>> Having just built world on 10.0-CURRENT FreeBSD 10.0-CURRENT #0 >>> r234370: Tue Apr 17 10:17:46 CEST 2012, gives me now a flooding of >>>=20 >>> <jemalloc>: Conf string ends with key >>>=20 >>> on console, screens, xterms with almost everything I touch. If those >>> messages, which I believe are surely necessary, could be focused on >>> the console and not bothering xterms, editors etc., would be nice = and >>> polite and would make the work even with a development branch more >>> convenient ... ;-) >>>=20 >>> What's up? How to avoid this message flooding? >>=20 >> remove /etc/malloc.conf >=20 > simple and efficient ;-) 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? JN
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D1956364-054B-4598-97EB-664D0EDB3B08>