Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Baggy Spandex

macrumors 6502
Original poster
May 23, 2009
392
350
A little while back, I residual issues from installing and uninstalling a Razer mouse and it's software. It seemed there was a 'daemon' that kept running that I found and trashed eventually. Now, when opening console I get this (focus on bold text), this is just a tiny sample of the list. The same processes keep on showing up repeatedly.

10/29/09 6:22:56 PM com.apple.launchd.peruser.501[80] (com.seagate.notificationexec.plist[539]) posix_spawn("/Library/Driver Support/NotificationExec.app/Contents/MacOS/NotificationExec", ...): No such file or directory
10/29/09 6:22:56 PM com.apple.launchd.peruser.501[80] (com.razer.DeathAdder.Daemon[540]) posix_spawn("/Library/PrivilegedHelperTools/RazerDeathAdderDaemon.app/Contents/MacOS/RazerDeathAdderDaemon", ...): No such file or directory
10/29/09 6:22:56 PM com.apple.launchd.peruser.501[80] (com.seagate.notificationexec.plist[539]) Exited with exit code: 1
10/29/09 6:22:56 PM com.apple.launchd.peruser.501[80] (com.seagate.notificationexec.plist) Throttling respawn: Will start in 10 seconds
10/29/09 6:22:56 PM com.apple.launchd.peruser.501[80] (com.razer.DeathAdder.Daemon[540]) Exited with exit code: 1
10/29/09 6:22:56 PM com.apple.launchd.peruser.501[80] (com.razer.DeathAdder.Daemon) Throttling respawn: Will start in 10 seconds
10/29/09 6:23:06 PM com.apple.launchd.peruser.501[80] (com.razer.DeathAdder.Daemon[542]) posix_spawn("/Library/PrivilegedHelperTools/RazerDeathAdderDaemon.app/Contents/MacOS/RazerDeathAdderDaemon", ...): No such file or directory
10/29/09 6:23:06 PM com.apple.launchd.peruser.501[80] (com.razer.DeathAdder.Daemon[542]) Exited with exit code: 1
10/29/09 6:23:06 PM com.apple.launchd.peruser.501[80] (com.razer.DeathAdder.Daemon) Throttling respawn: Will start in 10 seconds
10/29/09 6:23:06 PM com.apple.launchd.peruser.501[80] (com.seagate.notificationexec.plist[541]) posix_spawn("/Library/Driver Support/NotificationExec.app/Contents/MacOS/NotificationExec", ...): No such file or directory
10/29/09 6:23:06 PM com.apple.launchd.peruser.501[80] (com.seagate.notificationexec.plist[541]) Exited with exit code: 1
10/29/09 6:23:06 PM com.apple.launchd.peruser.501[80] (com.seagate.notificationexec.plist) Throttling respawn: Will start in 10 seconds

I know absolutely nothing about console or what goes on behind the scenes with OSX, and hopefully one of you guys will. What does this mean? Is something trying to run over and over again? The same messages pop up every other second. Is there anything I can do to stop this behavior?

The Razer mouse is long gone, but I can't seem to find any residual files left over from the install. Same with the Seagate stuff. I just use the HD as a HD, and thought I erased all the software. I also checked User Startup items, and there's nothing that's on the list for launching on startup.

What gives?
 
I am assuming you have removed the files that are listed in the log?

Such as:

Code:
/Library/PrivilegedHelperTools/RazerDeathAdderDaemon.app/Contents/MacOS/RazerDeathAdderDaemon

Code:
/Library/Driver Support/NotificationExec.app/Contents/MacOS/NotificationExec
 
I am assuming you have removed the files that are listed in the log?

Such as:

Code:
/Library/PrivilegedHelperTools/RazerDeathAdderDaemon.app/Contents/MacOS/RazerDeathAdderDaemon

Code:
/Library/Driver Support/NotificationExec.app/Contents/MacOS/NotificationExec

Yessiree
 
Just making sure. Typically, it isn't a good idea to delete these things willy nilly. Launchd is still trying to launch these items.

Look in /Library/LaunchAgents, /Library/LaunchDaemons, or /Library/StartupItems and remove the Launch Agent that is calling up the Razer and Seagate software. They should be relatively obvious.
 
Hmmm....thanks for the tip. Just trashed and deleted those files (they did exist), but they keep on trying to launch...weird?
 
Log out and back in, so launchd (yours, not the one with PID 1) can restart. (don't kill it while you're still logged in, it will kill everything without actually logging you out. You can still log out with shift+cmd+q, which is how I got out of it. :p)
 
Nevermind, sorry. I spent a while looking for the problem files mentioned above, but they were only present after a combination of logging in and out. Once I located the files and deleted them, all was well.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.