syslogd and bzip2 hogs after 6.3 to 7.0 upgrade

Kris Kennaway kris at
Sat Mar 8 12:57:44 UTC 2008

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?


More information about the freebsd-questions mailing list