From owner-freebsd-stable@FreeBSD.ORG Tue Jun 8 07:10:32 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66B8116A4CE for ; Tue, 8 Jun 2004 07:10:32 +0000 (GMT) Received: from freebsd.takeda.tk (node-402413e2.sna.onnet.us.uu.net [64.36.19.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3480143D54 for ; Tue, 8 Jun 2004 07:10:32 +0000 (GMT) (envelope-from takeda@takeda.tk) Received: from takeda.lan (takeda.lan [10.0.0.3]) by freebsd.takeda.tk (8.12.11/8.12.11) with ESMTP id i587AVe6077654; Tue, 8 Jun 2004 00:10:31 -0700 (PDT) (envelope-from takeda@takeda.tk) Date: Tue, 8 Jun 2004 00:10:30 -0700 From: Dariusz Kulinski X-Mailer: The Bat! (v2.01) X-Priority: 3 (Normal) Message-ID: <18919733703.20040608001030@takeda.tk> To: "Kyle Mott" In-Reply-To: <000001c44d26$bc22a6a0$1414a8c0@kyle> References: <5719057546.20040607235913@takeda.tk> <000001c44d26$bc22a6a0$1414a8c0@kyle> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: Viewing SSH Connection X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2004 07:10:32 -0000 Hello Kyle, Tuesday, June 8, 2004, 12:03:43 AM, you wrote: > It was a kernel panic, but of course I didn't have enough space on /var: > Jun 7 23:41:59 smith savecore: reboot after panic: page fault > Jun 7 23:41:59 smith savecore: no dump, not enough free space on device > (261612 available, need 395776) > So, I'm SOL this time, but I'm freeing up space as I type, in case this > happens again (and checking my other systems to make sure they have > enough free space in /var too!) :D > As long as I do the 'kldunload snp.ko', I should be ok, right? Don't > need to worry about /dev/snp* ? actually when watch command is called I belive it automatically loads snp.ko. I don't know how you can protect against that, either erase snp.ko or maybe increase securelevel to 1 (man securelevel). But after that you won't be able to load/unload any module (there are also more restrictions) until you reboot your computer. -- Best regards, Dariusz mailto:takeda@takeda.tk CCNA, SCSA, SCNA, LPIC, MCP certified http://www.takeda.tk