How to tell what processes are driving I/O loads

launchd and the Login Items pane of Accounts preferences are the two places that normally start a process when you log in.

If you don't see the item in System Preferences -> Accounts -> specific account -> Login Items then you will have to look into launchd.

Basically the LaunchAgents and LaunchDaemons folders in ~/Library

Lastly, if they are not there, then it's a system level launchd task that you might want to use launchctl to show or look in /Library instead of the user level library.

Most people just have to manage the preference pane. Here is a snap of mine showing the Activity Monitor selected and ready to be deleted if I press the – button.

It is strange to see the questions between "windows migrated" and "default mac" users. :) Windows migrated users usually want "somewhat tweak" the system. Default Mac users - simply "using it".

I'm using MAC much years, and never needed to use the launchctl command. If mean never, mean in normal usage, of course sometimes needed use it when installing somethings from the macports - for onetime load of startup files or so.

I'm wondering, why you need start/stop/restart services with launchctl? Asking because if you not an experienced OS X users you probably will screw the system "harmony" :). So, in this case - IMHO - better to ask the specific problem, so ask how to start/stop the specific service.

As the answer - check first System preferences. Most common services are in the "Sharing" pane" - like web-server, sshd, CD sharing and so on...

Some third party dmg files with GNU stuff comes with own preference pane too. For example, you can install precompiled MYSQL server with a preference pane, what allow you start-restart the server.

If you don't find the wanted service in prefs, be more precise. What service you need start/stop? The "launchctl" command works as needed to work, ActivityMonitor too. You ofc can use "ps axuwww" or "top" commands from the Terminal too.

Remember, your now in the UNIX world, so nearly anything can be done from the command-line, but usually thats mean really much learning.. ;)

EDIT:

try:

sudo kill -1 204
              ^-process number

from the terminal, or simply kill the daemon from the ActivityMonitor. The watchdog should restart it.

Have you any lighthttpd file in the /Library/LaunchDaemons/*? So, any output form the command:

ls /Library/LaunchDaemons | grep -i light

if yes, you can use the:

sudo launchctl unload /Library/LaunchDaemons/filename.plist
sudo launchctl load /Library/LaunchDaemons/filename.plist

command for stop/start.