Thanks for linking me to the background reading, that was very educational.
I see that I can use VirtualGL Transport to call my GL applications without
a remote desktop, but this will introduce latency between the client-side
2D X server, and the remote 3D X server. Perhaps a startup script on
On 4/5/18 8:26 PM, qwofford wrote:
> I am having problems with the way /opt/TurboVNC/bin/Xvnc is being
> launched by /opt/TurboVNC/bin/vncserver, however (which I will refer to
> as Xvnc and vncserver from here forward).
>> My /etc/lightdm/lightdm.conf:
TurboVNC is not designed to be started from
I've ditched the TigerVNC server. I'm now launching sessions from
/opt/TurboVNC/bin/vncserver, and using SSH tunneling for the simplest
possible solution as you suggest. I will absolutely pursue one of the more
advanced security configurations in the near future, so thanks for that.
I am
On 4/5/18 2:52 PM, qwofford wrote:
> I realized shortly after posting that I mis-spoke. Although I have
> tigervnc installed, I am using xinetd to launch Xvnc, /not/ tigervnc.
>
> |
> service xvnc_darwin
> {
> disable =no
> protocol =tcp
> socket_type =stream
> wait =no
> user =nobody
> server
I forgot to address your comment about /etc/gdm/Init/Default.
I added a line to echo some text into a file in /tmp/. It did not appear
when I restarted gdm. Since this server is not in production, I had the
opportunity to reboot it to be sure. Still no test file. It appears that
I will skip X-forwarding on my ssh connections, thanks for pointing that
out.
I realized shortly after posting that I mis-spoke. Although I have tigervnc
installed, I am using xinetd to launch Xvnc, *not* tigervnc.
service xvnc_darwin
{
disable = no
protocol = tcp
socket_type = stream
wait =
On 4/4/18 9:13 PM, qwofford wrote:
> I am having trouble launching applications with vglrun from a TurboVNC
> session. Server OS is Centos 7. Client OS is OSX. vnc server is
> TigerVNC/Xvnc. I followed the server configuration documentation for
> VirtualGL 2.5.2, section 6.1 documentation very
