Author Topic: killing background processes (Read 5101 times)

csonni · « **on:** February 23, 2003, 08:07:00 PM »

Is there any way of killing background processes such as bluetooth, of which I don't have any use for? Opening ProcessViewer displays all sorts of items that I question whether or not they can be shut off.

kps · « **Reply #1 on:** February 23, 2003, 08:38:00 PM »

Bluetooth is not part of any startup procedure, you must have turned it on yourself, so it should be as simple to just quit the Bluetooth utlity that's running.

As far as any other processes are concerned, they are there for a reason and most are owned by root. Aside from the fact that many of the obscure processes use very little on no CPU or memory resources it's a non issue. Oh, and don't mess with root's processes. Most are needed to run the system.

If any of the USER processes go haywire, then you have three options.

1. Force Quit the app if it is an app. (most will be)

2. Try killing the process in ProcessViewer

3. Do it in the terminal...

Get the Process ID (PID) number by using the ps -aux command.
Then use: kill PID if that does not work, try:
kill -9 PID

see: the built in unix manual for more info...

If all else fails....reboot!

csonni · « **Reply #2 on:** February 24, 2003, 04:37:00 AM »

Nope, I never touched anything to do with Bluetooth. But when I started up ProcessViewer, it showed Bluetooth on the list, and it was actually taking up 13% of my processor for just a minute or so. There was no indication of Bluetooth running in my Dock either.

kps · « **Reply #3 on:** February 24, 2003, 09:01:00 AM »

What is the exact process name?

Is it called TrueBlueEnvironment by any chance?

Bluetooth should not be running...

csonni · « **Reply #4 on:** February 24, 2003, 10:37:00 AM »

Yes- that's it/ TruBlueEnvironment. If it's not supposed to be running, then how do I disble it?

csonni · « **Reply #5 on:** February 24, 2003, 10:56:00 AM »

I just checked with Process Viewer again and now see the TruBlue Environment is not running. Yet how do I account for the time(s) is has been running?

swhitset · « **Reply #6 on:** February 24, 2003, 04:02:00 PM »

Good Call KPS

csonni, True Blue Environment is not the same as "Bluetooth" it is part of "Classic". Therfore, process viewer will only show it running when you have Classic running.

Steve

kps · « **Reply #7 on:** February 24, 2003, 09:11:00 PM »

Yup, I had a gut feeling. As Steve said, TruBlueEnvironment is the Classic layer, which, in earlier development stages (or maybe even in Rhapsody) was called "the Blue Box" layer.

Now that you know this, if ever you can't shut down the machine or classic is holding your machine hostage, kill this process if it's running and you should be able to recover into OS X.

News:

Author Topic: killing background processes (Read 5101 times)