Ah, actually now I'm recalling that I added the line for forcibly killing xwin.exe to the login script as a precaution. And never verified that it was necessary. It probably does shut down at log off as you describe (but leaves the lock and log files causing problems for future users).
Jon TURNEY wrote: > > On 11/10/2010 15:38, davidstvz wrote: >> The problem is, it continues running in the background with the >> permissions >> of the user that originally started it, and then other users can't do >> anything with it (even when the first user logs off and a new user logs >> on >> it continues running). > > If you really are logging off (and not using user switching), the XWin > process > really should be terminated. If it doesn't shutdown in response to the > WM_ENDSESSION it's sent, it'll be forcibly terminated. > > However, there seems to be a bug with Xwin that we don't shutdown cleanly > when > sent WM_ENDSESSION, and so leave behind the lock file and unix socket, > which > will cause a subsequent attempt to run Xwin by a different, non-privileged > user to fail. > > Thanks for reporting the problem. > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29954854.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
