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

 

 

Related Articles

 

 

Ovolab Phlink Adds Network Caller ID Announcements

Send Article to a Friend

Ovolab Phlink Adds Network Caller ID Announcements -- Ovolab's Phlink is a USB device that plugs into your phone line and, when bolstered by the Phlink software for Mac OS X, enables all sorts of fun telephony-related functions triggered by receiving a call. The recently released Phlink 1.5 adds a particularly cool and welcome feature that I've been wanting for a while - network caller ID, where a copy of Phlink running on a Mac connected to the Phlink device broadcasts caller ID information (you must have that service from your local phone company) for incoming calls to all other Macs running the Phlink software on the local network.

<http://www.ovolab.com/phlink/>
<http://db.tidbits.com/article/07511>

It's a brilliant feature and seems to work fine. The only confusing part is that the Phlink software erroneously implies, during installation, that it won't work without a Phlink device attached. One solution might be to have Phlink ask if it should install in minimal, network caller ID notification-only mode, if it doesn't detect a Phlink device during initial setup. The network caller ID notification is limited to a transparent window that appears and then disappears; the remote copy of Phlink doesn't seem to log the fact that a call came in or perform any actions based on the remote notification.

The primary competition for Phlink is Parliant's PhoneValet, which offers a roughly similar set of features for handling incoming calls, though PhoneValet doesn't yet have network caller ID notification. [ACE]

<http://www.parliant.com/>
<http://db.tidbits.com/article/07380>

 

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>