X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0	tests=AWL,BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,TW_TV,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <29954854.post@talk.nabble.com>
Date: Wed, 13 Oct 2010 09:57:36 -0700 (PDT)
From: davidstvz <davidst AT csc DOT lsu DOT edu>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin + xwin in win7 as unprivileged user?
In-Reply-To: <4CB5E31C.2070206@dronecode.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <29889419 DOT post AT talk DOT nabble DOT com> <29897721 DOT post AT talk DOT nabble DOT com> <4CACB164 DOT 70706 AT dronecode DOT org DOT uk> <29899035 DOT post AT talk DOT nabble DOT com> <AANLkTinMarwQT45rKczO=fy5BscciK2fB3tw_PA-HmyD AT mail DOT gmail DOT com> <29934689 DOT post AT talk DOT nabble DOT com> <4CB5E31C DOT 2070206 AT dronecode DOT org DOT uk>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


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