Date: Fri, 04 Dec 1998 04:41:51 -0800 From: Mike Smith <mike@smith.net.au> To: Bruce Evans <bde@zeta.org.au> Cc: scrappy@hub.org, ventrex.freebsd@UNDER.suspicion.org, freebsd-current@FreeBSD.ORG Subject: Re: syslogd@hub messages being broadcast... Message-ID: <199812041241.EAA00704@dingo.cdrom.com> In-Reply-To: Your message of "Fri, 04 Dec 1998 20:17:05 %2B1100." <199812040917.UAA16573@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> >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. Actually, it's usually symptomatic of something being unable to allocate memory to print/format the error message. This phenomenon is very familiar to anyone that's worked with a low-memory system under real load. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812041241.EAA00704>