Remember that unix treats devices as "files" and is reluctant to shut down while any "files" are still open. Do an ls -il in the /dev directory to see what's going on, look in particular for a clue that a device might have been left open. Look at the access dates to see if anything is really really old.
Remember that unix treats devices as "files" and is reluctant to shut down while any "files" are still open. Do an ls -il in the /dev directory to see what's going on, look in particular for a clue that a device might have been left open. Look at the access dates to see if anything is really really old.
It has nothing to do with the apps not quitting. They are not getting the Apple Event to quit, which would not happen until the user agreed to Logout ( when that dialog appears).
He is not getting that.
ajones, can you sample loginwindow when this happens
at the password prompt type in the user's password. should do this only in an admin account.
though this might be of no help i would suggest pulling the plug and pulling out or disconnecting every card,device connected to your system. i once had a bad pci card that made my system behave in this fashion. I have heard of bad video cards doing something similar. anyways good luck.
Comments
Originally posted by asdasd
Are you saying that absolutely nothing happens when you chose logout from the Apple Menu, or do you get some of the logout and it fails?
Absolutely nothing happens. That's it. Nothing. It just sits there
What I do is go into the terminal and kill processes and narrow down the culprit by killing them in batches until the problem disappears.
Also the process I was talking about before is the same as the one you displayed, in top it is truncated.
Could you also put a return in your code line so the formatting of this page returns to normal????
Have you repaired permissions lately?
Originally posted by KWSN_hgs
Remember that unix treats devices as "files" and is reluctant to shut down while any "files" are still open. Do an ls -il in the /dev directory to see what's going on, look in particular for a clue that a device might have been left open. Look at the access dates to see if anything is really really old.
Have you repaired permissions lately?
Permissions are repaired daily @ 4:00am
He is not getting that.
ajones, can you sample loginwindow when this happens
In terminal
sample loginwindow 2
aaron$ sample loginwindow 2
sample cannot find a process you have access to which has a name like 'loginwindow'
syntax: sample <pid/partial name> <duration (secs)> { <msecs between samples> } <options>
options: {-mayDie} {-wait} {-subst <old> <new>}*
-file filename specifies where results should be written
-mayDie reads symbol information right away
-wait wait until the process named (usually by partial name)
exists, then start sampling
-subst can be used to replace a stripped executable by another
Note that the program must have been started using a full path, rather than a
relative path, for analysis to work, or that the -subst option must be specified
Originally posted by ajones
I get this:
Code:
aaron$ sample loginwindow 2
sample cannot find a process you have access to which has a name like 'loginwindow'
syntax: sample <pid/partial name> <duration (secs)> { <msecs between samples> } <options>
options: {-mayDie} {-wait} {-subst <old> <new>}*
-file filename specifies where results should be written
-mayDie reads symbol information right away
-wait wait until the process named (usually by partial name)
exists, then start sampling
-subst can be used to replace a stripped executable by another
Note that the program must have been started using a full path, rather than a
relative path, for analysis to work, or that the -subst option must be specified
Oops! Forgot to run it as root:
root# sample loginwindow 2
2004-07-23 17:32:24.844 sample[1866] Couldn't start c++filt for C++ name demangling
Sampling process 209 each 10 msecs 200 times
Sample analysis of process 209 written to file /tmp/loginwindow_209.sample.txt
sudo sample loginwindow 2
Password:
at the password prompt type in the user's password. should do this only in an admin account.
Originally posted by asdasd
Right. loginwindow is a root app, so
sudo sample loginwindow 2
Password:
at the password prompt type in the user's password. should do this only in an admin account.
though this might be of no help i would suggest pulling the plug and pulling out or disconnecting every card,device connected to your system. i once had a bad pci card that made my system behave in this fashion. I have heard of bad video cards doing something similar. anyways good luck.