[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [policy-1.9-5] VNC module in X AVC
- From: Aleksey Nogin <aleksey nogin org>
- To: russell coker com au, "Fedora SELinux support list for users & developers." <fedora-selinux-list redhat com>
- Cc:
- Subject: Re: [policy-1.9-5] VNC module in X AVC
- Date: Sat, 20 Mar 2004 19:09:53 -0800
On 20.03.2004 18:56, Russell Coker wrote:
What exactly does Xvnc do?
It starts a "virtual" X server - it does not attemts to interact with
the local hardware, but it will listen on 6000+display port as a normal
X server (so the clients can connect) and it will listen on the
5900+display port, so that the vncviewer clients can connect (possibly
remote, possibly several simultaneously) and on port 5800+display for
http requests (essentially providing a Java version of the VNC client).
Does it do the same sort of stuff as when the user
runs "startx" but for remote display only?
This is different. Normally Xvnc is started by the /usr/bin/vncserver
script (there is also /etc/rc.d/init.d/vncserver script which might need
a separate treatment), which would first start Xvnc and then start
appropriate X clients to the newly created display.
--
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin cs caltech edu (office), aleksey nogin org (personal)
Office: Jorgensen 70, tel: (626) 395-2907
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]