From owner-freebsd-hackers Tue Jan 18 11: 3:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 57C9014EE2 for ; Tue, 18 Jan 2000 11:02:54 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA97683; Tue, 18 Jan 2000 13:02:50 -0600 (CST) (envelope-from dan) Date: Tue, 18 Jan 2000 13:02:50 -0600 From: Dan Nelson To: spork Cc: freebsd-hackers@FreeBSD.ORG, noc@inch.com Subject: Re: high load, nothing happening? (LONG) Message-ID: <20000118130250.A97656@dan.emsphone.com> References: <20000118105100.A79849@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from "spork" on Tue Jan 18 13:57:50 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 18), spork said: > > On Tue, 18 Jan 2000, Dan Nelson wrote: > > In the last episode (Jan 18), spork said: > > > I'm not sure what the problem is. You're 97% idle. Maybe the hosted > > web sites on this machine are slightly more active than the ones on the > > other box. You could always manually panic the box and see what those > > three processes on the run queue are, but it doesn't seem to be worth > > the effort. > > That's another thing, the box is idle as we've yet to move it into > production. Out of curiousity, how does one make a machine panic > manually? CTRL-ALT-ESC, and at the prompt type in 'panic'. You'll need DDB compiled into the kernel, and crashdumps enabled. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message