Message-ID: <4CACE56D.8000505@dronecode.org.uk>
Date: Wed, 06 Oct 2010 22:09:01 +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>
In-Reply-To: <29899035.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; 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 06/10/2010 18:31, davidstvz wrote:
> Jon TURNEY wrote:
>> On 06/10/2010 16:10, davidstvz wrote:
>>> 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.
>>
>> The log file issue is discussed and a workaround given at [1]
>>
>> The lock file should be removed on xwin exit, so should not be a problem
>> unless xwin is crashing for you, in which case report that problem.
>>
>> Making the lock file name unique per user is a non-solution, as it
>> prevents it
>> from locking against multiple simultaneous uses of the same display
>> number.
>>
>> [1] http://cygwin.com/ml/cygwin-xfree/2010-08/msg00090.html
>
> Ah, I see how that is a non-solution.  I should stick to what I know.
>
> In any case, XWin is not crashing per se, instead when I type "exit" from
> the initial xterminal and exit cygwin (or press the windows close button) it
> remains running in the background.  So to open it again, I have to first
> terminate it from the task manager which I suppose qualifies as a crash.

Is there some reason why you can't use the 'Exit' menu item from the 
right-click menu of the X icon in the system tray area?

XWin should also respond by shutting down cleanly if you send it SIGTERM, e.g. 
'killall XWin'

> I've solved the problem by scheduling a task to delete the log and lock
> files when any user logs in (well, to mostly delete; windows refuses to let
> me delete the socket file descriptor so I had to rename it to a random
> number).

-- 
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