Date: Sat, 14 Apr 2001 18:32:51 -0700 (PDT) From: dpelleg+bsd@cs.cmu.edu To: freebsd-gnats-submit@FreeBSD.org Subject: kern/26584: kernel boot messages aren't logged correctly on remote logger Message-ID: <200104150132.f3F1Wp834389@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 26584 >Category: kern >Synopsis: kernel boot messages aren't logged correctly on remote logger >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 14 18:40:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Dan Pelleg >Release: 4.3-RC2 >Organization: >Environment: FreeBSD k 4.3-RC FreeBSD 4.3-RC #7: Sat Apr 14 08:19:46 EDT 2001 root@k:/usr/obj/usr/src/sys/K i386 >Description: Machine "a" is set to syslog remotely to machine "b". On machine "b", the boot messages are broken into lines weirdly: Apr 14 21:02:37 a /kernel: Flushed all rules. Apr 14 21:02:37 a /kernel: 00100 Apr 14 21:02:37 a /kernel: allow Apr 14 21:02:38 a /kernel: ip Apr 14 21:02:38 a /kernel: from Apr 14 21:02:38 a /kernel: any Apr 14 21:02:38 a /kernel: to Apr 14 21:02:38 a /kernel: any Apr 14 21:02:38 a /kernel: via lo0 This also happens for the sysctl messages (from /etc/sysctl.conf), but most of the other messages seem OK. >How-To-Repeat: "*.* @b" in machine a's /etc/syslogd.conf "console.info /var/log/console.log" in machine b's /etc/syslogd.conf reboot a. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104150132.f3F1Wp834389>