Message-ID: <4CB5E31C.2070206@dronecode.org.uk>
Date: Wed, 13 Oct 2010 17:49:32 +0100
From: Jon TURNEY <jon.turney@dronecode.org.uk>
Reply-To: cygwin@cygwin.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: cygwin@cygwin.com
CC: davidst@csc.lsu.edu
Subject: Re: cygwin + xwin in win7 as unprivileged user?
References: <29889419.post@talk.nabble.com> <29897721.post@talk.nabble.com> <4CACB164.70706@dronecode.org.uk> <29899035.post@talk.nabble.com> <AANLkTinMarwQT45rKczO=fy5BscciK2fB3tw_PA-HmyD@mail.gmail.com> <29934689.post@talk.nabble.com>
In-Reply-To: <29934689.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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