cygwin + xwin in win7 as unprivileged user?
Is it possible to make Cygwin work with xwin as an unprivileged user. I'm even open to stupid hacks like making the entire Cygwin directory owned by the "Everyone" group. I tried that but then it couldn't create a socket needed after I ran 'startxwin'. Anyway to get this working without using "run as" admin? -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29889419.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin + xwin in win7 as unprivileged user?
We are an an AD, perhaps the inability to create a socket is coming from above. However, I have full admin rights on these machines so I ought to be able to adjust that if that is the case. I'll take a look. Meanwhile, I tried various other tricks to run the thing as admin without it asking for a password, but no dice. Charles Wilson-2 wrote: > > On 10/5/2010 1:22 PM, davidstvz wrote: >> >> Is it possible to make Cygwin work with xwin as an unprivileged user. >> I'm >> even open to stupid hacks like making the entire Cygwin directory owned >> by >> the "Everyone" group. I tried that but then it couldn't create a socket >> needed after I ran 'startxwin'. >> >> Anyway to get this working without using "run as" admin? > > I don't have a solution for you, but I ran into the same issue on WinXP; > I don't believe the problem ("can't create a socket") is Win7 specific. > Rather, I think it is a security policy setting: XWin runs fine for me > on XP and Vista at home -- but in our corporate environment, I get that > error. > > I think my company's IT wizards have decided that nobody should be able > to open a socket, unless the program doing so is specifically allowed to > do so. By them. > > Are you, by chance, trying to run XWin on a corporate network where you > might run into the same policy? If so, I'll leave it up to you to > wrestle with your own IT wizards over that... > > -- > Chuck > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29891341.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin + xwin in win7 as unprivileged user?
I have done additional testing on this problem and it seems that the first user to login and run 'startxwin' owns all of the log and lock files and this is what is causing the problem. The first user can continue using xwin without issues, but no other users can do it after that. If someone would upgrade xwin to to make these file names unique for each user it should solve the problem. Meanwhile, I'm envisioning several workarounds. -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29897721.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin + xwin in win7 as unprivileged user?
Jon TURNEY wrote: > > On 06/10/2010 16:10, davidstvz wrote: >> I have done additional testing on this problem and it seems that the >> first >> user to login and run 'startxwin' owns all of the log and lock files and >> this is what is causing the problem. The first user can continue using >> xwin >> without issues, but no other users can do it after that. >> >> If someone would upgrade xwin to to make these file names unique for each >> user it should solve the problem. Meanwhile, I'm envisioning several >> workarounds. > > The log file issue is discussed and a workaround given at [1] > > The lock file should be removed on xwin exit, so should not be a problem > unless xwin is crashing for you, in which case report that problem. > > Making the lock file name unique per user is a non-solution, as it > prevents it > from locking against multiple simultaneous uses of the same display > number. > > [1] http://cygwin.com/ml/cygwin-xfree/2010-08/msg00090.html > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > Ah, I see how that is a non-solution. I should stick to what I know. In any case, XWin is not crashing per se, instead when I type "exit" from the initial xterminal and exit cygwin (or press the windows close button) it remains running in the background. So to open it again, I have to first terminate it from the task manager which I suppose qualifies as a crash. I've solved the problem by scheduling a task to delete the log and lock files when any user logs in (well, to mostly delete; windows refuses to let me delete the socket file descriptor so I had to rename it to a random number). -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29899035.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin + xwin in win7 as unprivileged user?
It's a multiuser windows 7 lab environment where the only thing I can count on is that the individual users will do whatever they want to. I'm having to forcibly kill the x-windows process rather than just use a plain signal termination. It's ignoring a vanilla taskkill. I haven't tried kill from inside cygwin. >> On 06/10/2010 16:10, davidstvz wrote: >>> I have done additional testing on this problem and it seems that the >>> first >>> user to login and run 'startxwin' owns all of the log and lock files and >>> this is what is causing the problem. The first user can continue using >>> xwin >>> without issues, but no other users can do it after that. >>> >>> If someone would upgrade xwin to to make these file names unique for >>> each >>> user it should solve the problem. Meanwhile, I'm envisioning several >>> workarounds. >> >> The log file issue is discussed and a workaround given at [1] >> >> The lock file should be removed on xwin exit, so should not be a problem >> unless xwin is crashing for you, in which case report that problem. >> >> Making the lock file name unique per user is a non-solution, as it >> prevents it >> from locking against multiple simultaneous uses of the same display >> number. >> >> [1] http://cygwin.com/ml/cygwin-xfree/2010-08/msg00090.html > > Ah, I see how that is a non-solution. I should stick to what I know. > > In any case, XWin is not crashing per se, instead when I type "exit" from > the initial xterminal and exit cygwin (or press the windows close button) > it > remains running in the background. So to open it again, I have to first > terminate it from the task manager which I suppose qualifies as a crash. Is there some reason why you can't use the 'Exit' menu item from the right-click menu of the X icon in the system tray area? XWin should also respond by shutting down cleanly if you send it SIGTERM, e.g. 'killall XWin' > I've solved the problem by scheduling a task to delete the log and lock > files when any user logs in (well, to mostly delete; windows refuses to > let > me delete the socket file descriptor so I had to rename it to a random > number). -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29900929.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin + xwin in win7 as unprivileged user?
The problem is, it continues running in the background with the permissions of the user that originally started it, and then other users can't do anything with it (even when the first user logs off and a new user logs on it continues running). David Csaba Raduly-2 wrote: > > On Wed, Oct 6, 2010 at 7:31 PM, davidstvz wrote: >> >> In any case, XWin is not crashing per se, instead when I type "exit" from >> the initial xterminal and exit cygwin (or press the windows close button) >> it >> remains running in the background. So to open it again, I have to first >> terminate it from the task manager which I suppose qualifies as a crash. > > That's rather heavy-handed. You don't have to kill the X server to get > a new xterm. There are two separate entities here: the X server (whose > visible presence is the tray icon) and the xterm client with its > visible window. The X server startup just has this convenience feature > that allows you to have a terminal window right away. On my machine > I've disabled this; the X server is started at logon and I launch > terminal windows when I need them, from desktop shortcuts. > > Check the right-click menu of the X server: there should be a sub-menu > called "Applications", which should contain a menu item to launch an > xterm. This would remove the need to stop and relaunch the X server. > > -- > GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ L w++$ tv+ b++ DI D++ 5++ > Life is complex, with real and imaginary parts. > "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus > Torvalds > "People disagree with me. I just ignore them." -- Linus Torvalds > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29934689.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin + xwin in win7 as unprivileged user?
Ah, actually now I'm recalling that I added the line for forcibly killing xwin.exe to the login script as a precaution. And never verified that it was necessary. It probably does shut down at log off as you describe (but leaves the lock and log files causing problems for future users). Jon TURNEY wrote: > > On 11/10/2010 15:38, davidstvz wrote: >> The problem is, it continues running in the background with the >> permissions >> of the user that originally started it, and then other users can't do >> anything with it (even when the first user logs off and a new user logs >> on >> it continues running). > > If you really are logging off (and not using user switching), the XWin > process > really should be terminated. If it doesn't shutdown in response to the > WM_ENDSESSION it's sent, it'll be forcibly terminated. > > However, there seems to be a bug with Xwin that we don't shutdown cleanly > when > sent WM_ENDSESSION, and so leave behind the lock file and unix socket, > which > will cause a subsequent attempt to run Xwin by a different, non-privileged > user to fail. > > Thanks for reporting the problem. > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > -- View this message in context: http://old.nabble.com/cygwin-%2B-xwin-in-win7-as-unprivileged-user--tp29889419p29954854.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple