From owner-freebsd-hardware Sat Apr 20 8:33:27 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 46C9A37B416 for ; Sat, 20 Apr 2002 08:33:23 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id BAA26137; Sun, 21 Apr 2002 01:33:15 +1000 Date: Sun, 21 Apr 2002 01:33:42 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Peter Haight Cc: hardware@FreeBSD.ORG Subject: Re: Reading from the USB ugen device. In-Reply-To: <200204192256.g3JMueRg071185@wartch.sapros.com> Message-ID: <20020421012548.A22598-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 19 Apr 2002, Peter Haight wrote: > I did finally get the usb driver to print debug messages to the console and > syscons, but the volume of messages is overwhelming syslogd so many messages > are getting dropped. This is making it really hard for me to understand > what's going on. Is there some way to make the kernel log to a file instead > of to syslog? Or log more reliably? I think it wouldn't help much to log to a file -- the kernel message buffer may fill up before syslogd can read it if it is spammed with debug messages. A serial console connected to something with log facilities (I use som_term_prog | tee foo) works best here (use plain printf so that the messages get sent to the serial console synchronously). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message