From owner-freebsd-questions@FreeBSD.ORG Mon Mar 27 14:09:37 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5F3716A420 for ; Mon, 27 Mar 2006 14:09:37 +0000 (UTC) (envelope-from corwin@aeternal.net) Received: from amber.aeternal.net (amber.in.markiza.sk [62.168.76.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46F5643D6B for ; Mon, 27 Mar 2006 14:09:29 +0000 (GMT) (envelope-from corwin@aeternal.net) Received: from localhost (localhost.aeternal.net [127.0.0.1]) by amber.aeternal.net (Postfix) with ESMTP id B8D9BB950 for ; Mon, 27 Mar 2006 16:09:27 +0200 (CEST) Received: from amber.aeternal.net ([127.0.0.1]) by localhost (amber.aeternal.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04954-08 for ; Mon, 27 Mar 2006 16:09:27 +0200 (CEST) Received: from [192.168.0.30] (pleiades.aeternal.net [192.168.0.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by amber.aeternal.net (Postfix) with ESMTP id 0D6C9B94F for ; Mon, 27 Mar 2006 16:09:27 +0200 (CEST) Message-ID: <4427F1A1.4030803@aeternal.net> Date: Mon, 27 Mar 2006 16:07:29 +0200 From: Martin Hudec User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <3aaaa3a0603270522w437c63b3u25922a60232b258c@mail.gmail.com> In-Reply-To: <3aaaa3a0603270522w437c63b3u25922a60232b258c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at aeternal.net Subject: Re: server crashing/deadlocking X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: corwin@aeternal.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 14:09:37 -0000 Hello Chris, Chris wrote: > I also want to know by enabling console.log will it catch everything > that pops up on the screen and if no how do I do that? In /etc/syslog.conf look for line with console.info, uncomment it, and HUP down the syslogd process, or issue restart to /etc/rc.d/syslogd Martin