7 messages in org.freebsd.freebsd-currentRe: <jemalloc>: Conf string ends with...| From | Sent On | Attachments |
|---|---|---|
| O. Hartmann | Apr 17, 2012 1:41 am | |
| Ivan Klymenko | Apr 17, 2012 5:51 am | |
| O. Hartmann | Apr 17, 2012 5:57 am | |
| John Nielsen | Apr 17, 2012 12:10 pm | |
| Jason Evans | Apr 17, 2012 12:40 pm | |
| AN | Apr 17, 2012 2:05 pm | |
| Jason Evans | Apr 17, 2012 2:20 pm |
| Subject: | Re: <jemalloc>: Conf string ends with key | |
|---|---|---|
| From: | John Nielsen (lis...@jnielsen.net) | |
| Date: | Apr 17, 2012 12:10:26 pm | |
| List: | org.freebsd.freebsd-current | |
On Apr 17, 2012, at 8:58 AM, O. Hartmann wrote:
On 04/17/12 14:51, Ivan Klymenko wrote:
В Tue, 17 Apr 2012 10:42:13 +0200 "O. Hartmann" <ohar...@mail.zedat.fu-berlin.de> пишет:
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
<jemalloc>: Conf string ends with key
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 ... ;-)
What's up? How to avoid this message flooding?
remove /etc/malloc.conf
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
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"