From owner-freebsd-current Sun Jun 22 21:28:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10748 for current-outgoing; Sun, 22 Jun 1997 21:28:59 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10743 for ; Sun, 22 Jun 1997 21:28:53 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id VAA18670; Sun, 22 Jun 1997 21:26:37 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Sun, 22 Jun 1997 21:26:37 -0700 (PDT) From: Tom To: Lars Fredriksen cc: current@FreeBSD.ORG Subject: Re: Upping the dmesg buffer In-Reply-To: <199706230355.WAA00616@fredriks-1.pr.mcs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, Lars Fredriksen wrote: > Hi, > Currently the MSG_BSIZE in /usr/include/sys/msgbuf.h is defined > as 8K. Would anyone have huge objections to making this 10-12-14-16K? > > Right now if you have a fair amount of scsi devices on connected to the > machine (particularly if some of those devices have multiple luns) you > end up loosing a lot of information ( and that is without the -v option). > > I set mine currently to 16k and that works fine( just need a rebuild of > dmesg), and if this is something that people in general are not willing > to spend their memory for, then I'll just have to modify it locally. > > Just thought I'd ask what others needs are in this regard. > > Lars > -- > ------------------------------------------------------------------- > Lars Fredriksen fredriks@mcs.com (home) > lars@fredriks-1.pr.mcs.net (home-home) > Maybe it should be made into a kernel config item: options "MSGBUF=32767" and make the dmesg source able to deduce the size of the kernel buffer. Tom