From owner-freebsd-current Sat Jun 28 15:47:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07299 for current-outgoing; Sat, 28 Jun 1997 15:47:52 -0700 (PDT) Received: from aleste.lovett.com (root@aleste.lovett.com [193.195.45.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA07294 for ; Sat, 28 Jun 1997 15:47:48 -0700 (PDT) Received: from aleste.lovett.com [193.195.45.10] (ade) by aleste.lovett.com with esmtp (Exim 1.62 #1) id 0wi6HH-00006Q-00; Sat, 28 Jun 1997 23:47:35 +0100 To: dg@root.com cc: freebsd-current@freebsd.org Subject: Re: 3.0-current issues (build 97-06-28) Organization: Demon Internet Ltd. Reply-To: ade@demon.net In-reply-to: Your message of "Sat, 28 Jun 1997 06:42:07 PDT." <199706281342.GAA27918@implode.root.com> Date: Sat, 28 Jun 1997 23:47:35 +0100 From: Ade Lovett Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > Find VM_KMEM_SIZE in /sys/i386/include/vmparam.h and double it to 64MB. The >next problem you'll encounter is running out of kernel virtual memory, but >hopefully you'll get by for now. Many thanks, that seems to be working now (at least, the machine hasn't crashed in 6 hours or so, which is one hell of a lot better than previously :) And now, for another query. With the current -current, pstat -T falls over as follows: aleste 101# pstat -T 179/4136 files pstat: sysctl: KERN_VNODE: No such file or directory with a little bit of tracking down, this would appear to be because of the following code in sys/kern/vfs_subr.c, line 1858: ---------------------------------------------------------------------- /* * XXX * Exporting the vnode list on large systems causes them to crash. * Exporting the vnode list on medium systems causes sysctl to coredump. */ #if 0 SYSCTL_PROC(_kern, KERN_VNODE, vnode, CTLTYPE_OPAQUE|CTLFLAG_RD, 0, 0, sysctl_vnode, "S,vnode", ""); #endif ---------------------------------------------------------------------- This isn't really a big problem for me, since I only use pstat -T as a way of tracking swap file usage, and I can use swapinfo instead, but I'm a little confused as to why something that *seemed* to work flawlessy in 2.2.2-RELEASE has been commented out in 3.0-CURRENT. -aDe -- Ade Lovett, Demon Internet Ltd.