Bug 26584

Summary: kernel boot messages aren't logged correctly on remote logger
Product: Base System Reporter: dpelleg+bsd <dpelleg+bsd>
Component: kernAssignee: Mark Linimon <linimon>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description dpelleg+bsd 2001-04-15 02:40:00 UTC
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.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2008-01-26 00:39:37 UTC
State Changed
From-To: open->feedback

Does this issue still persist with recent versions of FreeBSD?  It sounds 
as though it was an ipfw problem, and there has been a lot of work done 
on that since the time this PR was submitted. 

(Suggested by: erandir) 


Comment 2 Mark Linimon freebsd_committer freebsd_triage 2008-01-26 00:39:37 UTC
Responsible Changed
From-To: freebsd-bugs->linimon

track.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2008-02-22 01:21:26 UTC
State Changed
From-To: feedback->closed

Submitter can no longer reproduce this problem.