From owner-freebsd-questions Sun Feb 1 20:10:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26201 for questions-outgoing; Sun, 1 Feb 1998 20:10:16 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26102 for ; Sun, 1 Feb 1998 20:09:08 -0800 (PST) (envelope-from markem@primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA04054 for ; Sun, 1 Feb 1998 21:09:06 -0700 (MST) Received: from xdsl-ip47-064.phx.primenet.com(207.218.25.64), claiming to be "dad" via SMTP by smtp02.primenet.com, id smtpd003972; Sun Feb 1 21:08:55 1998 Message-Id: <3.0.5.32.19980201210854.0098aba0@pop.primenet.com> X-Sender: markem@pop.primenet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 01 Feb 1998 21:08:54 To: questions@FreeBSD.ORG From: "M. Monninger" Subject: netstat -m Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" Can someone explain (or point me to some info on) the values displayed by netstat -m? I'm running FBSD 2.2.5 on a old 486 box, using it as a gateway/firewall between my home LAN and my xdsl line to my ISP. It's dedicated to that function...runs only natd and dhcpc, no users except for a console session via the serial port. It works very well except that every two or three days it locks up. No console messages or log messages, it just freezes, requiring a punch of the reset button. Someone here mentioned mbufs and netstat -m and I started watching it. All the resource usages displayed seem to be always growing. I'm beginning to wonder if it's leaking something and causing the lock-ups. As I understand it, those allocations are based on the MAXUSER value. It's set to 16 now. Anyone have any advice on this? Am I chasing a red herring? The vmstat values seem to be OK. Any comments will be appreciated. OTOH, I guess I could take the path of least resistance and set up a cron job to reboot every couple days... Thanks... Mark