Jerry Krinock <mailto:jerry at ieee.org> wrote (Thursday, April 17, 2008 6:02 AM -0700): >I did try ^removing^ the launchd configuration plist for this >nonexisting program, but, not surprisingly, that did not stop >the repeated attempts to launch it. Removing the .plist will have no effect once the configuration file has been read by launchd when it started up. You need to unload, remove, or stop the job via launchctl (see man launchctl). For the record, the correct way of removing a .plist is use 'launchctl unload <path/to/.plist>'. If you still have the .plist you can probably stop the job using 'launchctl remove <joblabel>' (look in the .plist file to find the <label> property). If you don't, just restart the system. -- James Bucanek