> -----Original Message----- > From: Preetham [mailto:[EMAIL PROTECTED]] > Hi All: > I have a few questions on how the Xvnc works. > The client sends rendering information to the XServer. The > Xserver then > based on the Display number writes it into the Frame buffer. If VNC > can handle multiple client connections(multiple displays) > each connection should have its > own instance of the Framebuffer(virtual fb).
Every Xvnc process has it's own framebuffer. The Xvnc process in the default distribution does not use the framebuffer of the local Xserver. Hence for multiple connections to the same Xvnc (same vnc-server) there is one (virtual) framebuffer. For multiple connections to different Xvnc-s (different vnc-servers) there are as manny (virtual) framebuffers as there are Xvnc processes. http://www.sourcecodecorner.com/articles/vnc/linux.asp ... to start a new server on the fly. It is presented for linux which is just an other unix. I bet you only need to adapt the /etc/services and /etc/inetd.conf files. To check if it might work: `Xvnc :4 -query localhost`. Details to the /etc/inetd.conf file: - use the path to your Xvnc binary. - add the fontpath (-fp ...) to reflect your local fontpath (`xrdb -q`) http://xf4vnc.sourceforge.net/ If you use the XFree86 Xserver: gives access to :0 http://www.hexonet.de/software/x0rfbserver/ If your Xserver uses the framebuffer device: gives access to :0 CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
