Todd Sankey wrote:
I recently upgraded and ran into this problem as well.
I watched the XWin.exe process using ProcMon from
sysinternals.com and it doesn't look like a problem of
directory / file / user permissions as the FAQ would suggest.
I've updated the FAQ entry a bit.
From ProcMon it looks like /tmp/.tX0-lock is being deleted
before it is moved.
Specifically, it is being opened with options: Synchronous IO
Non-Alert, Non-Directory File, Delete On Close
The file is then closed and re-opened and the re-open fails
because it no longer exists.
Thanks for the information.
As you can see from LockServer() function in
http://cgit.freedesktop.org/xorg/xserver/tree/os/utils.c, the sequence of
actions should be
open(tmp)
write()
close()
link(tmp,lock)
unlink(tmp)
and the failure seems to be that the link() doesn't succeed. So having the
file "delete-on-close" does explain what is seen.
Any insight into why "delete-on-close" is being requested?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
