Date: Sat, 08 Mar 2008 13:57:42 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Neil Darlow <neil@darlow.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade Message-ID: <47D28D46.4050108@FreeBSD.org> In-Reply-To: <47D28B8A.6040902@darlow.co.uk> References: <47D2670D.3020108@darlow.co.uk> <47D2792A.9000908@FreeBSD.org> <47D28B8A.6040902@darlow.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Neil Darlow wrote: > Hi, > > Kris Kennaway wrote: >> Again, it's not bzip2 that is your underlying problem. > > I can't see what else it could be. I watched newsyslog kick-in at > 11:00UTC to rotate logs and that's what happened. > > There was no esoteric hardware access, e.g. writing to DVD, happening at > the time so I'm at a loss to explain what's happening. Did you track down the cause of your interrupt storm? Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47D28D46.4050108>