![]() The original comment about the translucent menu fix did not mention ssh, and in any case for the reasons I mention killing windowserver makes it a bad idea in all cases. Carbon applications will probably behave badly, for instance.Īs for the guy who suggested I *read* the comment. ( I understand there is a difference between kill -hup and kill -9 which is way more dangerous since it is a kill, not an interrupt) as the other applications will be killed, or interrupted, and may not quit correctly, if at all. The new windowserver has it's own session which preious sessioned applications cannot connect to, so no windows.Įven *if* the windowserver can catch the interupt and kill it's process this is by no means the safest way of exiting. ![]() A busy process writing to disk will still be writing to disk, but invisible, after the windowserver is killed. The problem with killing the windowserver is that you may leave dummy processes around, as the windowserver is ( or was pre-leopard for what I know) the parent process of all applications which present GUI. Similarly the loginwinodow will exit cleanly ( unlike other applications) when the windowserver dies. The paradigm is : logout cleanly ( handled by loginwindow), loginwindow quits, windowserver sees the loginwindow go down, windowserver quits, launchd( or init in previous systems) relaunches loginwindow which tickles the windowserver to relaunch. In the older systems the relaunch of the loginwindow *also* causes the windowserver to relaunch. In which case mark this as a leopard fix. On previous systems the logout relaunches windowserver ( with no other users logged in, of course). Maye it is true in leopard, which I do not have yet, that the windowserver lives on as a process on logout. You can see all the available signals by typing kill -l, but play with care! WindowServer is the program that manages the graphical side of OS X.-HUP is a signal that usually says to the process that configuration files are changed and the process must be restarted.After 30 seconds, windows reboot will start. ![]() The dark side is that if you have more than one program with the same name, all programs will receive the kill signal. The above command will set a time out of 30 seconds to close the applications. killall is the same, but you can use the name of the program instead of its process ID (pid). kill is a program to send signals (terminate or just "signals") to Unix programs - and in OS X, all programs are Unix programs.Quit your open programs first! You have been warned. Sudo killall -HUP WindowServer Warning: All your opened programs will quit immediately! This is like a restart, but of only the graphical part of the system. I just do that in Terminal, with this command: However, you only really need to restart the WindowServer, which handles the graphical part of the system. It does not store any personal data.I see a lot of hints, such as the one to remove 10.5's translucent menu bar, that tell you to restart your computer for the changes to take effect. ![]() The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.
0 Comments
Leave a Reply. |