From owner-freebsd-current@FreeBSD.ORG Tue Jun 27 10:39:08 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13B0C16A401 for ; Tue, 27 Jun 2006 10:39:08 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F75043D45 for ; Tue, 27 Jun 2006 10:39:01 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id k5RAcxIR038740 for ; Tue, 27 Jun 2006 14:38:59 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id k5RAcxQF038739 for freebsd-current@freebsd.org; Tue, 27 Jun 2006 14:38:59 +0400 (MSD) (envelope-from yar) Date: Tue, 27 Jun 2006 14:38:58 +0400 From: Yar Tikhiy To: freebsd-current@freebsd.org Message-ID: <20060627103858.GD36941@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Subject: Logging to serial console broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2006 10:39:08 -0000 Hi all, For quite a while syslogd has been failing to log messages to a serial console on my CURRENT system. Sometimes the date/time part of a message appears only, sometimes the first letter of the month only, but mostly nothing appears on the console, albeit logging to /var/log/messages is OK. I had used to blame my console null-modem cable until I tried to restart syslogd. It began to log to the console OK when restarted. Can the serial console be in a special state confusing syslogd during the boot sequence? According to fstat, /dev/console isn't opened by syslogd until restarted, but syslogd complains of no errors at the boot time even if put in debug mode. Moreover, it tells in its debug output it's logging to the console: %logger -p user.err test_message %tail syslog.out logmsg: pri 13, flags 0, from dg, msg Jun 27 14:23:06 yar: test_message Logging to CONSOLE /dev/console Logging to FILE /var/log/messages logmsg: pri 166, flags 17, from dg, msg Jun 27 14:23:06 dg yar: test_message No such problem seen on the vty console. Did anybody see anything similar? -- Yar