Start/Stop/Remove Daemons/Agents on Mac

If you have log messages like

Nov 4 23:29:13 idea com.apple.launchd.peruser.501[181] (de.novamedia.NML2NDeviceObserver[7664]): posix_spawn("/Applications/launch2net/launch2net.app/Contents/MacOS/NML2NDeviceObserver.app/Contents/MacOS/NML2NDeviceObserver", ...): No such file or directory
Nov 4 23:29:13 idea com.apple.launchd.peruser.501[181] (de.novamedia.NML2NDeviceObserver[7664]): Exited with exit code: 1
Nov 4 23:29:13 idea com.apple.launchd.peruser.501[181] (de.novamedia.NML2NDeviceObserver): Throttling respawn: Will start in 10 seconds
Nov 4 23:29:13 idea com.apple.launchd.peruser.501[181] (com.akamai.client.plist[7665]): Bug: launchd_core_logic.c:4139 (24108):13
Nov 4 23:29:13 idea com.apple.launchd.peruser.501[181] (com.akamai.client.plist[7665]): posix_spawn("/Applications/Akamai/loader.pl", ...): No such file or directory
Nov 4 23:29:13 idea com.apple.launchd.peruser.501[181] (com.akamai.client.plist[7665]): Exited with exit code: 1
Nov 4 23:29:13 idea com.apple.launchd.peruser.501[181] (com.akamai.client.plist): Throttling respawn: Will start in 10 seconds

in your /var/log/system.log, you should stop and remove the agents/daemons which causing these warnings, by doing this:

launchctl stop de.novamedia.NML2NDeviceObserver
launchctl remove de.novamedia.NML2NDeviceObserver
launchctl stop com.akamai.client.plist
launchctl remove com.akamai.client.plist 

launchctl is a tool that controls the system-wide and per-user launchd daemon/agent manager.

Comments

Post a Comment

Popular posts from this blog

Apple's evaluating a new JVM

To boost the Java performance on x64 Mac systems, Apple is evaluating a new Java VM  that is derived the BSD port. You can try the new JVM using the  -XXaltjvm=bsdserver VM args which is available in the recent JDK/JRE developer preview. Using this new VM may improve the Java performance and increase benchmark scores but performance drawbacks can be expected as well.
Read more

Tuning ext4 for performance with emphasis on SSD usage

The obligatory disclaimer: The more performance you gain, the more data integrity you loose! But if you want to tune something like a file system, I strongly assume that you know what you are doing :) These tips apply to all major Linux distributions like Fedora/Red Hat, OpenSUSE, and Ubuntu that are already using ext4 or are going to make ext4 their default file system. As write operations on Solid State Disks (SSD) are expensive the tips below are focused on SSD usage but also apply to HDD usage as well . My Ubuntu 9.04 Jaunty /etc/fstab after a fresh installation: [...] UUID=d818ddf9-ff01-e21a-a67d-3ceab43a9e2b / ext4 relatime,errors=remount-ro 0 1 UUID=0d339122-74e0-e0ea-805a-7879b1fa3172 /home ext4 relatime 0 2 [...] My tuned Ubuntu 9.04 Jaunty /etc/fstab : [...] UUID=d818ddf9-ff01-e21a-a67d-3ceab43a9e2b / ext4 noatime,barrier=0,nobh,commit=100,nouser_xattr 0 1 UUID=0d339122-74e0-e0ea-805a-7879b1fa3172 /home ext4 noatime,barrier=0,data=writeback,nobh,commit=100,nouser_xattr 0 2...
Read more