This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: Unable to delete .X11-unix\X0 file
- From: Harold L Hunt II <huntharo at msu dot edu>
- To: cygwin-xfree at cygwin dot com
- Date: Mon, 11 Aug 2003 09:03:45 -0400
- Subject: Re: Unable to delete .X11-unix\X0 file
- References: <3F37914F.5000706@gmc.ulaval.ca>
- Reply-to: cygwin-xfree at cygwin dot com
Boris Mayer-St-Onge wrote:
Hi everybody,
We have Cygwin 1.3.22-1 installed on a Windows XP sp1 machine with
XFree86 4.3.0-1. The computer is part of a domain and can be use by
several users.
The installation on Cygwin/XFree86 has been done as follow :
1- As Administrator, we have installed Cygwin/XFree86 on a local D:\
drive (so not at the standard folder).
2- We have edited the file usr\X11R6\bin\starxwin.bat to set correctly
the variable CYGWIN_ROOT.
You shouldn't need to do that if you are running startxwin.bat from the
d:\ drive and Cygwin was installed to d:\cygwin. On the other hand, if
you used a directory other than d:\cygwin, you would have to set
CYGWIN_ROOT.
When we run Cygwin/XFree86, everything is correct for everybody.
Unfortunately, when a user close his session without exiting
Cygwin/XFree86, the file tmp\.X11-unix\X0 is not deleted. When an other
user try to open Cygwin/XFree86, the application doesn't start since the
file tmp\.X11-unix\X0 is present and the user is not able to delete it.
As administrator I must then delete the file.
I have try to modify the permissions on folder tmp and tmp\.X11-unix to
allow users to delete the XO file but I doesn't work.
So my questions are :
1- Is the above situation normal?
2- If not, what should I forget to do during the installation and
configuration?
3- If yes, is it possible to allow users to delete XO file?
Thanks in advance for suggestions and answers.
Short of an administrative permissions fix (which I still think should
work), I can only suggest that maybe it is time we start trapping the
logoff/shutdown messages and call GiveUp when this happens. I would
think that Windows would send the WM_QUIT or WM_CLOSE message to all
open applications in these cases, but I could be wrong. Are the users
simply turning the machine completely off? If so, then you would need
to retrain the users before looking for other solutions.
Harold