On 03/19/2009 06:52 PM, Mark Post wrote: >>>> On 3/19/2009 at 12:20 PM, Steffen Maier <ma...@linux.vnet.ibm.com> wrote: > -snip- >> Since I was also interested whether RHEL provides such an HTTP served VNC >> client, I confirmed that this does not seem to be the case: > > This appears to be controllable via /etc/sysconfig/vncservers > > -snip- >> The java class files of the VNC client to be served are not part of the >> install image: > > I would say that /usr/share/vnc/classes/vncviewer.jar would provide the > needed functionality.
Sorry, I was only referring to the installation process, not the installed system. Thanks for pointing out the difference, Mark. For an installed RHEL system, you just need to allow incoming traffic on the TCP ports 5801 and 5901 (assuming the VNC server drives display :1) using /usr/bin/setup. After this, you may dynamically start a vncserver using the command line tool "vncserver" or of course persistently configure the startup of a vncserver as mentioned by Mark. I tried the former and it was accessible on port 5901 with a VNC client and on port 5801 with a Java-capable web browser. Steffen Linux on System z Development IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Erich Baier Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
