X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.7 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,TW_TV
X-Spam-Check-By: sourceware.org
Message-ID: <4CAF450C.1000908@dronecode.org.uk>
Date: Fri, 08 Oct 2010 17:21:32 +0100
From: Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
Reply-To: cygwin AT cygwin DOT 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 AT cygwin DOT com
CC: davidst AT csc DOT lsu DOT edu
Subject: Re: cygwin + xwin in win7 as unprivileged user?
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> <4CACE56D DOT 8000505 AT dronecode DOT org DOT uk> <29900929 DOT post AT talk DOT nabble DOT com>
In-Reply-To: <29900929.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

On 06/10/2010 22:15, davidstvz wrote:
> It's a multiuser windows 7 lab environment where the only thing I can count
> on is that the individual users will do whatever they want to.  I'm having
> to forcibly kill the x-windows process rather than just use a plain signal
> termination.  It's ignoring a vanilla taskkill.  I haven't tried kill from
> inside cygwin.

Yes, there seems to be a bug with Xwin that is doesn't respond correctly to 
being non-forcibly killed by taskkill.  Thanks for drawing my attention that :-)

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

I should perhaps mention that if the existence of the lockfile really causes 
problems, you can always use the -nolock option.

>>> [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).

Likewise, you can avoid the creating of the unix domain socket with '-nolisten 
unix', but I think then you'll need to explicitly include localhost in DISPLAY 
environment variable setting (e.g. DISPLAY=localhost:0.0)

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