Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling Take Control ebooks.

 

 

Pick an apple! 
 
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.

Visit Discussion of syslogd problem at Smarticus

 
 

Real World Word Problem Solved

Send Article to a Friend

Several years ago, when I worked at Microsoft answering questions about Word for the Mac, people frequently called in to ask about an annoying "System memory too low to run Word" error message that would appear when they launched Microsoft Word 5.x. This message left users with no alternative but to try launching Word again. This problem happens even if the Mac in question has plenty of free RAM available.

Microsoft could never come up with a truly satisfactory solution, though you can try juggling your memory situation by installing or removing extensions, launching or quitting other programs, or allocating a different amount of RAM to Word. Sometimes trying to launch Word a second or third time would work; sometimes launching other programs first (like the Alarm Clock or Key Caps) would solve the problem. I still use Word 5 for some word processing tasks, and I run into this situation probably 20 percent of the time when I try to launch the program. Microsoft has published its specific comments about the error in a Knowledge Base article, which you can read on the Web.

<http://www.microsoft.com/kb/deskapps/word/ q109263.htm>

A potentially more satisfactory fix is now available, though. Written by Larry Rosenstein, the freeware extension FixWordSystemMemory 1.1, should correct the problem by, as Larry explains it, "allocating and immediately freeing a block of memory in the system heap when Word starts up (it does not do anything until you launch Word)." Word has launched smoothly for me since I installed the extension, though I don't use Word often enough to vouch for the extension's complete success. According to Larry, version 1.1 has some improvements over 1.0 that make the extension more successful, and the 3K download shouldn't take long.

<ftp://mirrors.aol.com/pub/info-mac/text/fix- word-system-memory-11.hqx>

[The technique used by FixWordSystemMemory is commonly called a "memory bubble." By allocating and immediately releasing a piece of memory in the system heap before Word launches, FixWordSystemMemory creates a "bubble" of free memory for Word to use which otherwise may not have been free. Ironically, Microsoft has used the same technique in some of its other applications, and yes, it's common for programs to need a bit of memory in the system heap for their own use. -Geoff]

 

Make friends and influence people by sponsoring TidBITS!
Put your company and products in front of tens of thousands of
savvy, committed Apple users who actually buy stuff.
More information: <http://tidbits.com/advertising.html>