X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<29897721.post@talk.nabble.com>
Date:	Wed, 6 Oct 2010 08:10:56 -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:	<29889419.post@talk.nabble.com>
MIME-Version:	1.0
References:	<29889419 DOT post AT talk DOT nabble DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

I have done additional testing on this problem and it seems that the first
user to login and run 'startxwin' owns all of the log and lock files and
this is what is causing the problem.  The first user can continue using xwin
without issues, but no other users can do it after that.

If someone would upgrade xwin to to make these file names unique for each
user it should solve the problem.  Meanwhile, I'm envisioning several
workarounds.
-- 
View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29897721.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

- Raw text -