Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Possible Duplicate:
bash process uses 90% CPU, comes back on computer restart

A bash script is starting on my Macbook air. (I bought it yesterday).

The script is taking about 20% of my cpu.

It starts every time I restart the machine.

I want to know what it's running ... but I don't know how to find out.

[I can very slowly find my way around terminal, but I've not done unix stuff for about 15 years ... and then I was no expert.]

share|improve this question

marked as duplicate by slhck, Daniel Beck, Mokubai, studiohack Jun 23 '12 at 17:44

This question was marked as an exact duplicate of an existing question.

What script is it? There might be a very good reason why it's running. – Kenneth Hoste Jun 23 '12 at 12:57
Kenneth: that's what I'm trying to figure out. I can see it in Activity Monitor, it's taking 20% of my CPU, and I have no idea why. – clarke ching Jun 23 '12 at 12:59
How do you know it is running and which user is running it? – Mark Jun 23 '12 at 12:59
Not enough detail in the question. Why do you assume it's a bash script? How are you measuring 20% CPU usage - is the script staying alive long enough for you to see it in Activity Monitor? – username Jun 23 '12 at 13:00
-1, this question is unclear. Please at least tell us the name of that script. It's impossible to even guess what happens if you can't supply that important piece of information. What does the Activity Monitor show about that script? Please edit your question and add more info. Maybe also show the output of ps auxww related to that script. – slhck Jun 23 '12 at 13:08

Maybe you just left running when you shut down your Mac? In Lion open apps are reopened when you reboot

share|improve this answer
I figured it out (thanks to this: bash process uses 90% CPU, comes back on computer restart). It was Amazon's Send To Kindle application. I installed it, but it didn't uninstall a script. I've reinstalled it and now the problem has gone away. Thanks everyone. – clarke ching Jun 23 '12 at 13:16

Not the answer you're looking for? Browse other questions tagged .