[OpenIndiana-discuss] It was so easy... Re: xvnc-inetd only accepting one connection in total?? Huh??

[Hans J. Albertsson]

So easy.... I think ???

ck-seat-tool -a  --display-type=LocalVNC  --session-type=LoginWindow

Repeat suitable number of times, and you get the ability to run 
suitable-number separate sessions. Or do you??

Quirk remaining: There's a timeout..?? Is that in gdm, or in Xvnc or in 
the login itself or in the shell? Or am I totally off, and this is not 
the way to do it?? and I'm just seeing that it doesn't really do what I 
think it does?

On 2013-03-02 09:58, Hans J. Albertsson wrote:
> Thanks.
>
> The SunRay system assigns display numbers dynamically, sort-of (it's a 
> kludge, really, I know, but it acts as if it were true), so I was 
> thinking this mechanism should have been a natural for any interface 
> designer when TigerVNC appeared..
>
> I THINK I understand how to do this via console-kit and GDM, (Thanks 
> Mr Palo!) in a way that at least won't require me to assign special, 
> different commands to each prospective user, but rather will manage a 
> limited set of possible displays in a sort of dynamic manner.
>
> Which is reasonable.
>
> For Mr Harvey: I don't think the port is used in that fashion when in 
> nowait state: Displays can, I think, use any type of channel, pipes or 
> unix sockets or tcp sockets, to talk to the X clients and any port 
> number can be disassociated from the socket used to communicate 
> between the caller and whatever service the port server initiated on 
> behalf of the caller.
> And as far as I can see, the xvnc man page says that in nowait and 
> inetd mode, Xvnc's port is only used when prompting the initiation of 
> a service, not for running it. Then again, I'm not really an X expert.
>
>
> On 2013-03-01 23:19, Alan Coopersmith wrote:
>> On 03/ 1/13 01:57 PM, Hans J. Albertsson wrote:
>>> So it's a bad bad bad design under the hood, and the manual lies or 
>>> is at least
>>> very incomplete.
>>>
>>> Or what?
>> Sorry, you're reaching the limit of what I remember about this 
>> mechanism, since
>> it's been years since I've really worked with it.
>>
>>> BTW I haven't been able to find any document actually describing the 
>>> "-once"
>>> option to "Xvnc -inetd". Where should I look for that?
>> Xserver(1):
>>       -once   causes the server to terminate (rather  than reset)
>>               when the XDMCP session ends.
>>
>
> I suddenly feel very dense... :-) Sorry...
>
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss