Ask Different is a question and answer site for power users of Apple hardware and software. 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

I almost always boot up in Verbose mode so I can see what's happening during boot up/shut down. Usually critical errors make themselves obvious, some lesser errors aren't so obvious but can be cleared up, and yet other errors aren't really errors at all and should be expected. I've fixed a bunch of things on startup, and now I'm trying to figure out messages I see on shutdown.

I'm basically just wondering if anyone can be an interpreter and tell me if any of this is bad or should not be happening, or if it all just looks normal.

Sorry for posting these messages as a photo. I'm not sure where to find a text log, if there is one:

enter image description here

It looks like there are a lot of processes that are staying alive until the system finally gives up on them and kills them all. If this is to be expected, that would be helpful to know. If not, how can I make the shut down run more smoothly?

Oh, and can anyone explain the anonymous.sudo processes? Is that okay? Where might that come from?

Thanks for any illumination you can offer!

share|improve this question
Log files are in /var/log – patrix Jun 4 '12 at 7:33
You can use to look at the log files – Mark Jun 4 '12 at 15:15
up vote 0 down vote accepted

It depends on each executable.

The closedown process sends a signal SIGTERM to each process and the process should then cleanup and shut itself down. This includes subprocesses and that appears to be most of the lines in your log - perhaps the parent does not shut its subprocesses down when it does, also see Unix zombie processes in wikipaedia

I would suggest that the original parent has not behaved 'properly' but probably does not matter unless there become many more zombie processes when the OS could run out of process handles.

share|improve this answer
So how might I find the parent process? How might I make it "behave?" How many zombies are too many? Is the answer just that none of these errors matter and I can ignore them? answer I would be fine with. – iynque Jul 30 '12 at 1:55
You cannot always find the parent as it might be killed off, to fix it look at the source code of the app, there is a fixed number of processes ands threads but depends on OS e.g. and you can ignore them but I would be wary of an app that left many zombies as what else does it do wrong? – Mark Jul 30 '12 at 10:21

Interpreting error messages is not far removed from reading tea leaves. Having said that, I would start by uninstalling (or at least updating) your copy of TaoEffect Espionage. It looks like it installs a driver of some sort which is failing to quit.

share|improve this answer
You think all of this is due to Espionage? I suppose I could change to a different solution for encrypted folders if that would solve the whole thing. I can't give up privacy/security, but I don't have to use Espionage to get it. Espionage was just included in a bundle, so I had it before I knew I would need it and have used it ever since. :D – iynque Jul 30 '12 at 1:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.