256N/A###############################################################################
1584N/A# Copyright (c) 2007, 2015, Oracle
and/or its affiliates. All rights reserved.
256N/A# Permission is hereby granted, free of charge, to any person obtaining a
919N/A# copy of this software and associated documentation files (the "Software"),
919N/A# to deal in the Software without restriction, including without limitation
919N/A# the rights to use, copy, modify, merge, publish, distribute, sublicense,
919N/A#
and/or sell copies of the Software, and to permit persons to whom the
919N/A# Software is furnished to do so, subject to the following conditions:
919N/A# The above copyright notice and this permission notice (including the next
919N/A# paragraph) shall be included in all copies or substantial portions of the
919N/A# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
919N/A# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
919N/A# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
919N/A# THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
919N/A# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
919N/A# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
919N/A# DEALINGS IN THE SOFTWARE.
256N/A# Excerpts from Technical Product Training and Sustaining TOI docs for
256N/AArchitecture and Implementation
822N/A The open source TigerVNC release is built using the Xorg server sources
256N/A to provide the X server portion of the sources for Xvnc. This provides
256N/A an Xvnc that includes the same features as Sun's Xorg, including Sun
1584N/A enhancements like IA Extension support & Xserver DTrace probes.
256N/A 1. Please provide a brief description of the feature and how it is used.
256N/A VNC provides a remote desktop session viewing protocol (RFB protocol).
256N/A RFB clients, better known as VNC viewers, are available for most
256N/A platforms, in both open source and commercial flavors. The Vino
256N/A project in JDS (LSARC 2006/371) already delivers in Solaris a VNC server
256N/A that can capture the display from a running session on a normal X server.
256N/A This project delivers Xvnc, an X server that displays to a Remote Frame
256N/A Buffer (RFB) protocol client over the network, without requiring an
256N/A existing X server session displayed on local video hardware. It also
822N/A delivers the TigerVNC vncviewer to connect to remote VNC servers, and
256N/A several associated programs for managing these.
256N/A 2. Does this feature EOL any other feature or does it offer an alternative
256N/A to another existing feature?
256N/A The vncviewer provided by this project replaces the vncviewer script
256N/A delivered by the Vino project (LSARC 2007/391) in several Nevada builds,
256N/A but which was not yet included in any Solaris or SXDE release.
256N/A 3. Please list any dependencies on other features.
256N/A 4. Is the feature on or off by default? What considerations need to be
256N/A The Xvnc server is off by default. Considerations before enabling are
256N/A documented in the man page and the ARC case security questionairre.
256N/A 5. Is this a platform specific feature and if so which platform?
256N/A Please provide any differences in behaviors or functionality of the
256N/A feature if it is supported on the x86 platform.
256N/A 6. Please list the minimum system requirements.
981N/A System running Solaris 10U5 or later.
256N/A 7. List the things (GUI, commands, packages, binaries, configuration files,
256N/A etc.) that are introduced, removed, or have substantially changed by
256N/A this feature or project.
1088N/A S10 package SUNWvncviewer /
256N/A 8. What major data structures have changed or have been added?
256N/A 9. Please list any header file changes.
256N/A 10. Are there known issues or bugs with this feature? If so, please provide
256N/A bug Ids and any known workarounds.
256N/A 11. How would one recognize if the new feature is working or not working?
256N/A (Note: The engineer will provide as much information as possible at
256N/A this time. For the latest information, please refer to the appropriate
256N/A System Administration document.)
256N/A Can a VNC client (such as vncviewer) connect to a VNC server (such as
256N/A Xvnc) and see the desktop session in it?
1088N/A See full test case instructions below.
256N/A 12. Are there any diagnostic tools for this feature and what are they?
256N/A Xvnc contains the same Xserver DTrace probes as the other Solaris
256N/A X servers. No other diagnostic tools are known at this time.
256N/A 13. Are there any unique conditions or constraints to Licensing,
256N/A Localization, and Internationalization?
256N/A 14. Please provide a pointer to the following:
822N/A PSARC/2009/592: TigerVNC 1.0
256N/A o Documentation Plan: Man pages from open source release
256N/A 16. If available, please provide a pointer to the cookbook procedures
256N/A for installation and configuration.
981N/AUpdated from test case instructions in bugster bug id 6572087,
981N/Athese are several common ways of configuring Xvnc to run:
981N/A1) Starting on demand from inetd, displaying graphical login screen:
981N/A a) If using dtlogin (Solaris 10):
981N/A # Enable XDMCP connections on dtlogin by removing "-udpport 0" from args
981N/A # Warning: restart will kill all current dtlogin sessions!
981N/A svcadm refresh cde-login
981N/A svcadm restart cde-login
981N/A If using gdm (optional in Solaris 10, default in later releases):
981N/A If it wasn't already there, then run "svcadm restart gdm" to activate.
981N/A ( Warning: restart will kill all current gdm sessions!)
981N/A b) For either dtlogin or gdm:
981N/A # (it was added in snv_99 but is not in any S10 update release)
981N/A # Enable Xvnc inetd service:
981N/A Connect from another machine with:
981N/A and verify you see the login screen and can login to a desktop session.
981N/A2) Starting at system boot from display manager, displaying login screen:
981N/A a) Add a display1 instance of x11-server service for configuration
981N/A and configure it to run Xvnc:
981N/A b) If using dtlogin (Solaris 10):
981N/A # Configure dtlogin to start it
981N/A If using gdm 2.30 or later (snv_130 or later):
981N/A ck-seat-tool -a --display-type=Local display=:1
981N/A c) Connect from another machine with:
981N/A and verify you see the login screen and can login to a desktop session.
981N/A3) Starting manually, displaying session of user who started it, requiring
981N/AVNC password (separate from Unix login password, not securely encoded on
981N/Adisk or across the network, so don't use a valuable password):
981N/A From another machine, open a web browser and go to
981N/A (Assuming vncserver said it was starting on display :2 - if it listed
981N/A another display number, change :5802 to 5800 + the display id.)
981N/A Enter the password you provided to the vncserver script when it asked
981N/A and verify you see a simple desktop session in the viewer.
981N/A When done testing, kill the session with:
981N/A (again, substituting display value as necessary)
981N/A x0vncserver --SecurityTypes=None
981N/A Connect from another machine with:
981N/A and verify you see and can control the existing session you ran