Randy,
I would recommend passing on to Brian the following "not as easy as it
might first appear" mini-topic, and I would also include a caution
that if this topic is covered, that it be abbreviated in every way
possible(eg creating and providing online documents or slides that
would be only quickly skimmed during presentation) because it'd be
easy to turn the topic into an entire night...
TigerVNC - Setting up the Server
Overall Problem:
Since the balkanization of VNC, each version is often very different
from every other so a good amount of documentation and procedures is
no longer common to all, particularly server-side. The TigerVNC
documentation for setting up the Server, particularly for different
client configurations is incomplete, unclear and next to useless. But,
TigerVNC really does have a lot to offer compared to other flavors of
VNC.
Specific TigerVNC topics not documented well...
First a short background...
TigerVNC servers can be set up 3 different ways
Xvnc (seems to be set up by default)
x0vncserver (apparently favored by many)
vncserver invoked from CLI (apparently favored by old timers who set
up this way a decade ago and never want to change)
Specific TigerVNC unclear topics
With Xvnc,
2 configurations are already set up by default on ports 5901 and 5801
4 other configurations are possible but you might need to create or
activate (my guess by copying the systemd unit files of existing and
modifying but that's not entirely clear, eg if this is true than why
only 6 total configs? Is it true 4 other configs might somehow exist
but are disabled and could cause contention or are those 4 slots to be
configured and conflicting config enabled?)
Small comment:
With the previous version of TigerVNC, the default setup referenced a
config file (IIRC /etc/vnc.config)
This file was simple to configure,
It included the two default active configs for 5901 and 5801, and
sample disabled configs for the other 4 ports. You could simply modify
and enable each or even add additional configs based on the others as
templates. Everything "just worked."
But, apparently this is no more and now instead of a single
configurable VNC server, it appears that following the direction of
many other Linux projects, the server has been eliminated and clients
connect to UNIX and Network sockets directly.
Bottom line...
Can't say for others, but I'd be happy if just the following were revealed...
For Xvnc,
- Clarification about the 6 vnc configurations (2 already enabled).
- Are there existing configurations available and simply need to be enabled?
- When creating a new configuration, should a port be configured that
won't conflict with a disabled configuration if such exists?
- Is there a way to display all active and disabled configurations?
If it's your(Brian's) preference to set up one of the other ways, I'd
like to see it
Sources
ArchWiki TigerVNC
https://wiki.archlinux.org/index.php/TigerVNC
openSUSE Documentation
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.vnc.html
Thx,
Tony
On Mon, Jul 16, 2018 at 3:49 PM, Randall Shimizu
Post by Randall ShimizuBrian six has agreed to do a presentation on SUSE and OpenSuse possbly
in August. So I want to know what topic on SUSE or OpenSuse people
would like to see...? Otherwis Brian Six will have a presentation
ready or we ask and determine what potential topics we people want to
hear about at the next meeting.
--
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
--
KPLUG-***@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list