Re: HEADSUP: /etc/malloc.conf format change

2012-04-26 Thread Ruslan Ermilov
On Wed, Apr 25, 2012 at 10:43:59AM -0700, Jason Evans wrote: > On Apr 25, 2012, at 9:39 AM, Ruslan Ermilov wrote: > > So you removed _malloc_options that was part of the documented > > programming API, while some software made use of it. [...] > > Please explore the possibility to add backwards com

Re: HEADSUP: /etc/malloc.conf format change

2012-04-25 Thread Mark Linimon
On Wed, Apr 25, 2012 at 09:37:36PM -0700, Tim Kientzle wrote: > The Ports maintainers will run "experimental" ports builds on the > port build clusters to help verify potentially disruptive changes > like this before they are committed. Well, actually, portmgr@. Send a PR with [exp-run] in the Sy

Re: HEADSUP: /etc/malloc.conf format change

2012-04-25 Thread Tim Kientzle
On Apr 25, 2012, at 10:43 AM, Jason Evans wrote: > > On a related note, is there any way to find all ports that refer to > _malloc_options without extracting source for all of them? I considered > being proactive about finding software that depends on _malloc_options, but > no tractable appr

Re: HEADSUP: /etc/malloc.conf format change

2012-04-25 Thread Jason Evans
On Apr 25, 2012, at 9:39 AM, Ruslan Ermilov wrote: > So you removed _malloc_options that was part of the documented > programming API, while some software made use of it. > > While removing part of the documented API was definitely a bad > idea, you didn't provide any mean to detect this change >

Re: HEADSUP: /etc/malloc.conf format change

2012-04-25 Thread Ruslan Ermilov
On Tue, Apr 17, 2012 at 12:34:20PM -0700, Jason Evans wrote: > As a result of the recent jemalloc update, the format for > /etc/malloc.conf has changed. If your system has an old-style > /etc/malloc.conf, you will want to delete it prior to > installworld, and optionally re-create

HEADSUP: /etc/malloc.conf format change

2012-04-17 Thread Jason Evans
As a result of the recent jemalloc update, the format for /etc/malloc.conf has changed. If your system has an old-style /etc/malloc.conf, you will want to delete it prior to installworld, and optionally re-create it using the new format after rebooting. See malloc.conf(5) for details

Re: No man page for /etc/malloc.conf ?

2003-01-24 Thread Attila Nagy
Hello, > Where can I find the definitions for the AJ, aj, HR<, etc. that are > being discussed in the 'performance' thread? In malloc(3): http://www.freebsd.org/cgi/man.cgi?query=malloc&apropos=0&sektion=0&manpath=FreeBSD+5.0-current&format=html man malloc --[ Free Software ISOs - http:/

No man page for /etc/malloc.conf ?

2003-01-24 Thread walt
Where can I find the definitions for the AJ, aj, HR<, etc. that are being discussed in the 'performance' thread? Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: malloc.conf (was Re: Performance problems with 5.0-RELEASE)

2003-01-23 Thread Erik Trulsson
On Thu, Jan 23, 2003 at 02:14:46PM -0500, Rahul Siddharthan wrote: > Dan Nelson wrote: > > > # ls -l /etc/malloc.conf > > > lrwxr-xr-x 1 root wheel 4 Jan 23 11:52 /etc/malloc.conf -> HR< > > > > H and < should only make a difference if you are low o

Re: malloc.conf (was Re: Performance problems with 5.0-RELEASE)

2003-01-23 Thread Dan Nelson
In the last episode (Jan 23), Rahul Siddharthan said: > Dan Nelson wrote: > > > # ls -l /etc/malloc.conf > > > lrwxr-xr-x 1 root wheel 4 Jan 23 11:52 /etc/malloc.conf -> HR< > > > > H and < should only make a difference if you are low on memory. >

malloc.conf (was Re: Performance problems with 5.0-RELEASE)

2003-01-23 Thread Rahul Siddharthan
Dan Nelson wrote: > > # ls -l /etc/malloc.conf > > lrwxr-xr-x 1 root wheel 4 Jan 23 11:52 /etc/malloc.conf -> HR< > > H and < should only make a difference if you are low on memory. Yes. > R is on > by default in 5.0 anyway, due to A and J being on by defa

Re: malloc.conf

2000-03-25 Thread Arun Sharma
On Sat, Mar 25, 2000 at 12:11:50PM -0800, Jordan K. Hubbard wrote: > > I did and created malloc.conf as documented there. And things were > > fine after that. Wouldn't it be better if the build process created > > a default /etc/malloc.conf ? > > It's purely an

Re: malloc.conf

2000-03-25 Thread Poul-Henning Kamp
gt;> >> Please read the malloc(3) manual page. >> >> >> > >> >I did and created malloc.conf as documented there. And things were >> >fine after that. Wouldn't it be better if the build process created >> >a default /etc/malloc.conf ? &

Re: malloc.conf

2000-03-25 Thread Arun Sharma
On Sat, Mar 25, 2000 at 09:05:18PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Arun Sharma writes: > >On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote: > >> > >> Please read the malloc(3) manual page. > >> > >

Re: malloc.conf

2000-03-25 Thread Jordan K. Hubbard
> I did and created malloc.conf as documented there. And things were > fine after that. Wouldn't it be better if the build process created > a default /etc/malloc.conf ? It's purely an optional file; one doesn't need to be installed by default in order for things to behav

Re: malloc.conf

2000-03-25 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Arun Sharma writes: >On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote: >> >> Please read the malloc(3) manual page. >> > >I did and created malloc.conf as documented there. And things were >fine after that

Re: malloc.conf

2000-03-25 Thread Arun Sharma
On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote: > > Please read the malloc(3) manual page. > I did and created malloc.conf as documented there. And things were fine after that. Wouldn't it be better if the build process created a default /etc/malloc.conf ?

Re: malloc.conf

2000-03-25 Thread Poul-Henning Kamp
Please read the malloc(3) manual page. In message <[EMAIL PROTECTED]>, Arun Sharma writes: >After upgrading to 4.0 from source, I had a simple program which called >malloc core dump on me. After ktrace'ing it and creating /etc/malloc.conf >it was happier. > >Bu

malloc.conf

2000-03-25 Thread Arun Sharma
After upgrading to 4.0 from source, I had a simple program which called malloc core dump on me. After ktrace'ing it and creating /etc/malloc.conf it was happier. But I can't find malloc.conf anywhere in /usr/src. How does it get created during the build ? -Arun To Unsubsc