public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: sledz@zone42.org Subject: Re: CygwinX at MS Terminalserver? Date: Fri, 13 Aug 2010 11:15:00 -0000 [thread overview] Message-ID: <4C6527D3.3000303@dronecode.org.uk> (raw) In-Reply-To: <4C64F0A8.5020400@zone42.org> On 13/08/2010 08:13, Steffen Sledz wrote: > Am 12.08.2010 18:04, schrieb Jon TURNEY: >> On 12/08/2010 08:31, Steffen Sledz wrote: >>> Does anyone has experiences running CygwinX at an MS >>> Terminalserver? We like to use it at one based on Windows >>> Server 2003 with NTFS. >>> >>> Is it possible to run multiple XWin instances for multiple >>> user sessions in parallel? >>> >>> Any suggestions how to setup the rights in /tmp, /var/log, >>> /var/run, etc.? >> >> You shouldn't change the rights on any of these, as this could >> affect the security or functioning of other cygwin apps. >> >> Fortunately, you shouldn't need to, as, provided each X server >> instance has a unique display number, everything should work :-) > > This seems not to be right. :( > > Here are the results of my tests: > [snip] > > Now testuser0002 tries to start another server in parallel. This gives this error: > > /usr/bin/startxwin: Resource temporarily unavailable (errno 11): Another X server instance is running on DISPLAY :0 This is expected. As I said, each X server instance must have a unique display number. This can't possibly work any other way. If two users both have an X server with display number 0, to which server should a client started with DISPLAY=:0.0 connect? > Now testuser0001 stops his server by using the "Exit" item from the server menu. After this the files/dirs look like this. [snip] > /var/log: > total 2316 > drwxrwxrwt+ 1 Administrator Administrators 0 Aug 13 08:54 . > drwxr-xr-x+ 1 Administrator Administrators 0 May 17 16:21 .. > -rw-r--r-- 1 Administrator Administrators 139786 Aug 13 08:48 setup.log > -rw-r--r-- 1 Administrator Administrators 2219958 Aug 13 08:48 setup.log.full > -rw-r--r-- 1 testuser0001 Domain Users 4871 Aug 13 08:58 XWin.0.log > ------------>snap<---------------- > > Now testuser0002 tries to start a server. This results in an error popup: > > ------------>snip<---------------- > A fatal error has occured and Cygwin/X will now exit. > > Cannot open log file "/var/log/XWin.0.log" This is interesting. On my systems, /var/log has mode 777, rather than 1777. Having the restricted deletion flag set on /var/log prevents other users from deleting the logfile from a previous run. However, checking the source for setup.exe, I see that it does create /var/log with 1777 permissions, so how I got into this state I don't know... I'm not sure that is right, but assuming it is intentional, I guess we need to create a /var/log/xwin with mode 777 and arrange for that to be the default logfile location mkdir /var/log/xwin chmod 777 /var/log/xwin adding '-logfile /var/log/xwin/XWin.%s.log' to your xwin command line. -- 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/
next prev parent reply other threads:[~2010-08-13 11:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-12 7:31 Steffen Sledz 2010-08-12 16:07 ` Jon TURNEY 2010-08-13 8:23 ` Steffen Sledz 2010-08-13 10:39 ` Hermann-Josef Beckers 2010-08-13 11:15 ` Jon TURNEY [this message] 2010-08-16 10:14 ` Steffen Sledz 2010-08-27 16:32 ` Jon TURNEY 2010-09-20 14:21 ` Jon TURNEY 2010-09-20 14:26 ` [PATCH] os: Add -displayfd option Jon TURNEY 2010-09-20 14:27 ` [PATCH] Handle X server -displayfd option transparently Jon TURNEY 2010-08-13 21:07 ` CygwinX at MS Terminalserver? Kurt Franke
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4C6527D3.3000303@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=sledz@zone42.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).