Re: Increase size of dmesg buffer?

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        Hello.  Are you looking for 
options MSGBUFSIZE, documented in the options(4) man page? I see:

     options MSGBUFSIZE=integer
     This option sets the size of the kernel message buffer.  This buffer
     holds the kernel output of printf() when not (yet) read by syslogd(8).
     This is particularly useful when the system has crashed and you wish
to
     lookup the kernel output from just before the crash.  Also, since the
     autoconfig output becomes more and more verbose, it sometimes happens
     that the message buffer overflows before syslogd(8) was able to read
it.
     Note that not all systems are capable of obtaining a variable sized
mes-
     sage buffer.  There are also some systems on which memory contents are
     not preserved across reboots.

This was from a 5.0 man page, but I've used it for many years.  Is it gone
in -current?
-Brian
On Jun 27,  7:03pm, Paul Goyette wrote:
} Subject: Increase size of dmesg buffer?
} I'm trying to debug some acpi stuff on a fairly large system, and the 
} default 32KB of "NVRAM" dmesg space does't seem to be enough - some of 
} the important early stuff gets rolled-over before I can capture it.
} 
} So, it there some undocumented option that can be used to increase the 
} allocated space?  Is there any limitation on how much space can be used?
} 
} 
} 
} -------------------------------------------------------------------------
} | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
} | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
} | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
} | Kernel Developer |                          | pgoyette at netbsd.org  |
} -------------------------------------------------------------------------
>-- End of excerpt from Paul Goyette