From owner-freebsd-stable@FreeBSD.ORG Sat May 17 14:12:26 2003 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 7A9AD37B401 for ; Sat, 17 May 2003 14:12:26 -0700 (PDT) Received: from port995.com (port995.com [213.162.97.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D3BA43FAF for ; Sat, 17 May 2003 14:12:25 -0700 (PDT) (envelope-from sansan@cas.port995.com) Received: by port995.com (Port995 Mail, from userid 77) id ADDD91407663; Sat, 17 May 2003 22:12:12 +0100 (BST) Received: from cas.port995.com (Authenticated SMTP client) by port995.com (Port995 Mail) with ESMTP id 824AC14076AF for ; Sat, 17 May 2003 22:12:11 +0100 (BST) Message-ID: <3EC6A5C2.1060903@cas.port995.com> Date: Sat, 17 May 2003 22:12:34 +0100 From: Santos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.75.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Syslogd and serial console bug? 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: Sat, 17 May 2003 21:12:26 -0000 Hi all. Bug bin/8865 strikes again? I have a FreeBSD 4.8 Release machine. After sometime, the logs just aren't modified, syslogd just doesn't log. The last entry on /var/log/messages is from may 15. Could this be caused to use a serial console (-P on /boot.config, no keyboard attached) to access the machine? There was once a time that when i Control^D'ed on the serial console and a lot of messages, obviously threw by syslogd, scrolled by, messages that should be loged to the console and /var/log/messages. Some output: # syslogd -d -ss off & running.... init cfline("*.err;kern.debug;auth.notice;mail.crit /dev/console", f, "*", "*") Killed syslogd and commented out the line "*.err;kern.debug;auth.notice;mail.crit /dev/console" on /etc/syslogd.conf, and guess what... # syslogd -d -ss **insert explosion of messages from may 15, may 16 and may 17 here!** So it probably was caused by the serial console :). Doesn't the -P flag on /boot.config takes care of "telling" the rest of the system that now the console is a serial one? Having ttyd1 on /etc/ttys doesn't work for me, had to use cuaa1 instead, to have a working serial console. Maybe this cause the bug? Santos