Gmane User wrote:
Larry Hall (Cygwin X) wrote:
Gmane User wrote:
<snip>
Which made me think "wouldn't it be nice if mounting didn't have
to be done for each user account?". I install cygwin on whatever
machine (of several) that I happen to work on, so such a global
fix would make life easier. And there is a solution.
With a bit of refresher from the unix shell newsgroup, I was
prompted into realizing that startxwin.sh launches XWin in the
background, which allows the PID to be captured with "$!". So
if one really wanted to, startxwin could use "wait" with XWin's
PID to wait for XWin to finish, after which it deletes
/tmp/.X11-unix. No need to maintain user-specific /tmp mounts.
One could probably create a start-menu shortcut that invokes
startxwin.sh with the run command, similar to the way it is used
in startxwin.bat.
If memory serves me correctly, this was talked about before and perhaps
even implemented. If the latter is actually true, then it got lost at
some point (perhaps about the time that the Cygwin-X maintainer was
lost ;-) ).
Yeah, well, it's probably not the end-all-be-all solution. It occured
to me that if the startxwin.sh script got interrupted somehow e.g. due
to forced shutdown, power outage, logoff, or "kill", then it never runs
the command that erases /tmp.X11-unix.
Yeah, it may have been some combination of what you suggested and some
additional "magic" on the front end to pick up on those cases. I'm sure
it's in the email archives somewhere.
Are you the new maintainer?
Let me check... Nope! :-)
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
--
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/
