On 03/02/2010 19:43, Jon TURNEY wrote:
I had the same symptoms. Non-administrator WinXP users couldn't start
the XWin Server, and no /var/log/XWin.0.log was created. The log file
could get created if there wasn't one already present, which led me to
put the log file in the user's directory instead of /var/log. The
other problem was that users couldn't create the /tmp/.X0-lock file
and /tmp/.X11-unix/X0 socket if they were left by another user. The
solution was to give each user their own /tmp directory.
I fixed it with the following:
1. Added a line in /etc/profile, just before the "chmod 1777 /tmp" line:
mount -f "$USERPROFILE/Local Settings/Temp" /tmp
2. Changed the XWin Server icon so instead of just startxwin.exe, it
says:
... "startxwin.exe -- -logfile ~/XWin.log"
(Don't take out the beginning of the command that runs startxwin
through bash, or the /etc/profile won't get run. The quotes are
needed because this is the argument to bash's -c option.)
Could any of the guru's comment on how good or bad these solutions are?
Thanks. It's long been suspected that there is some problem with
lockfiles running XWin as a non-administrator user (See FAQ 3.4,[1]),
but I've never had a sufficient clear description to understand what the
problem is, until now.
Okay, thanks to having some useful reproduction steps I've done a bit of
testing and generated some patches (at [1]) which should hopefully address
some of these issues.
The thing I don't understand at this stage is that the /tmp/.X0-lock file and
/tmp/.X11-unix/X0 socket should be removed when the X server shuts down, so
shouldn't be causing problems. Is there some specific way the server is being
exited which doesn't remove these files?
[1] http://sourceware.org/bugzilla/show_bug.cgi?id=9778
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
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/