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
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 a
en'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
>>>
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 pro
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 woul
sking 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
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 "
7 matches
Mail list logo