macOS Command Line – Get List of Currently Running Processes

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.

Testing seems to show that the culprit is Intel's Turbo Boost technology, which disables processor cores on the fly without telling the OS. Since they aren't running the CPU idle process, activity monitor doesn't account for them, and it appears that the machine is under 50% idle when the reality is that it's near 100% idle.

At the moment it doesn't appear as though this can be easily disabled or controlled under OS X: How can I disable CPU throttling and CPU disabling?

Turbo boost is built into many Core i7 and i5 processors, and some of the latest Core i3 processors. You will have to check your processor version against intel's list of Turbo Boost capable processors to find out if yours has it. If you don't have sandy bridge, you probably don't have turbo boost.