Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Dec 2011 15:21:06 -0700
From:      Charlie Martin <crmartin@sgi.com>
To:        <freebsd-stable@FreeBSD.org>
Cc:        Eric Richards <erichards@sgi.com>, Larry Fenske <LFenske@sgi.com>, crmartin@sgi.com, "Peter W. Morreale" <morreale@sgi.com>, Jeremy Chadwick <freebsd@jdc.parodius.com>
Subject:   PRINTF_BUFR_SIZE=4096?
Message-ID:  <4EF4FED2.6020909@sgi.com>
In-Reply-To: <20111223000705.GA6242@icarus.home.lan>
References:  <4EF3B790.5050509@sgi.com> <20111223000705.GA6242@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
In the course of looking at Jeremy's reponse to my query about a mystery 
panic, I noted his recommendation that PRINTF_BUFR_SIZE be set to 256.  
Ever-obedient, I went to set the value, and discovered instead that the 
conf file already has it set to 4096.

As he says below, there are concerns about setting the value too high 
causing "major issues".

I being Christmas and all I hate to ask Jeremy to dig up the post he 
mentioned, but wonder if anyone can clue me in on what the major issues 
might be?

Thanks, and regards

Charlie Martin

On 12/22/2011 05:07 PM, Jeremy Chadwick wrote:
> Also, be aware that the above stack trace is interspersed.  Ultimately
> you get to clean up the output yourself.  This is a long-standing
> problem with FreeBSD which can be helped but only slightly/barely by
> using "options PRINTF_BUFR_SIZE=256" in your kernel configuration (the
> default configs have a value of 128.  Do not increase the value too
> high, there are concerns about it causing major issues; I can dig up the
> post that says that, but I'd rather not).

-- 

Charles R. (Charlie) Martin
Senior Software Engineer
SGI logo
1900 Pike Road
Longmont, CO 80501
Phone: 303-532-0209
E-Mail: CRMartin@sgi.com <mailto:CRMartin@sgi.com>
Website: www.sgi.com <http://www.sgi.com>;




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF4FED2.6020909>