After extensive testing coordinated with TidBITS Talk participants in California and confirmed today, we've discovered the rolling blackouts currently plaguing San Francisco-area residents can cause Apple's just-released Mac OS X to kernel panic under specific circumstances. Reader reports from MacInTouch and MacFixIt corroborate our findings that having your iDisk mounted in Mac OS X (just choose iDisk from the Finder's Go menu) when there's a brief network flicker due to power switching from the area power grid to Apple's data center generators can cause Mac OS X to kernel panic. Examination with a packet sniffer showed timing to be important - the crash happens only when Mac OS X tries to start reading data from a mounted iDisk when it's unavailable, only to have it appear immediately thereafter. Luckily, the workaround is simple - only mount your iDisk when you're planning to use it, and dismount it afterwards by dragging it to the Trash (which morphs into an Eject icon when disks are dragged to it) when you're done. This unfortunate behavior jives with our experience of causing Mac OS X to kernel panic within 10 minutes after installation by trying to download iTunes from an iDisk, accidentally mounting the iTunes self-mounting image thanks to double-clicking more than necessary due to poor performance, and then force quitting Disk Copy and relaunching the Finder several times.
Syslogd Overwhelming Your Computer?
If your Leopard (Mac OS X 10.5) system is unexpectedly sluggish, logging might be the culprit. Run Activity Monitor (Applications/Utilities/ folder), and click the CPU column twice to get it to show most to least activity. If syslogd is at the top of the list, there's a fix. Syslogd tracks informational messages produced by software and writes them to the asl.db, a file in your Unix /var/log/ directory. It's a known problem that syslogd can run amok. There's a fix: deleting the asl.db file.
Launch Terminal (from the same Utilities folder), and enter these commands exactly as written, entering your administrative password when prompted:
sudo launchctl stop com.apple.syslogd
sudo rm /var/log/asl.db
sudo launchctl start com.apple.syslogd
Your system should settle down to normal. For more information, follow the link.
- April Fools Day Apologies (02 Apr 01)