From owner-freebsd-current  Fri Dec  4 01:17:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA11851
          for freebsd-current-outgoing; Fri, 4 Dec 1998 01:17:29 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11843
          for <freebsd-current@FreeBSD.ORG>; Fri, 4 Dec 1998 01:17:26 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA16573;
	Fri, 4 Dec 1998 20:17:05 +1100
Date: Fri, 4 Dec 1998 20:17:05 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199812040917.UAA16573@godzilla.zeta.org.au>
To: scrappy@hub.org, ventrex.freebsd@UNDER.suspicion.org
Subject: Re: syslogd@hub messages being broadcast...
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>I usually see that when swap is about to completely fill up and the system
>is on it's way to a downward load/swap spiral. 

Perhaps it is caused by the broken line buffering in syslogd.  MAXLINE is
1024, so syslog will insert bogus line breaks whenever the message buffer
contains more than about 1024 characters.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message