How enable or install xVNC on OpenIndiana 148

VNC comes in at least two forms for Unix/OpenIndiana/Solaris/Linux/etc. It can run as a user process after you have logged into the xserver, or xVNC can run out of the super server (inetd/xinetd etc).

The pros to the VNC option is that you can secure your desktop with a password. The con is that it doesn’t start up automatically when you are not logged in.

In contrast, xVNC becomes available via the super server so that when X11 server comes up, you can log in via VNC.

The VNC package setup is easy in OpenIndiana 148. Install the package. Run it from System->Preferences->Desktop Sharing and then follow the prompts.

The xVNC install even easier.

pkg install xvnc
svcadm enable xvnc-inetd

Now test it. Voila. Easy peasy.

This entry was posted in Linux, OpenIndiana, VNC, X11, xVNC and tagged , , . Bookmark the permalink.

4 Responses to How enable or install xVNC on OpenIndiana 148

  1. Daren Green says:

    Hello,

    Have just switched to OI-151a for my storage solution, managed to solve some driver issues with my LSI 9240-8i and everything is working fine… except Xvnc.

    Using the first method you describe to enable desktop sharing once I’m logged in works fine, but as this machine will eventually sit headless somewhere, the second method was more useful.

    Installed the xvnc package, enabled the service with no problems. However when I attempt to connect to the server from another machine on the network, the vnc client sees the xvnc server and brings up the presumably default sized 1024×768 window, where I was hoping to see the gdm login, but it is in fact just a black screen. After a short while the vnc client closes the window.

    Do you know if there anything else that needs to be done to make this work?

    Cheers.

  2. Daren Green says:

    Hey, me again,

    Thought I’d post a quick follow-up in case anyone gets a hit here to pass on how I eventually got it working.

    Found an old guide from Tim Thomas here, that helped getting things working as I wanted. A few things needed changing for OI151a however:

    1. xvnc was already clearly installed and enabled on my system, so skipped past obtaining and installing the required package.
    2. And /etc/services had the corresponding entry already to enable inetd to do it’s thing – so no changes needed here.
    3. The location of my custom.conf on oi151a was /etc/gdm/custom.conf – just entered the correct lines in the xdmcp and security sections, leaving the rest blank.
    4. I restarted the services as they were already enabled – just not working as intended.
    5. Connecting from another machine gave me the gdm login screen.
    6. I did want a persistent session, so I did almost everything as described,

    # svccfg -s xvnc-inetd
    svc:/application/x11/xvnc-inetd> setprop inetd/wait = boolean: true

    this sets the correct field without the need to go into a vi session, you can verify it’s been changed accordingly with listprop command before exiting svccfg.

    #svcadm refresh xvnc-inetd to reload the changed config and reconnecting with a vnc client gave me a persistent session. Did notice a consistent ~20% cpu usage even when there was no client connected and the session was still running though – something to look into another day.

    Cheers.

  3. Pingback: Homepage

Leave a Reply

Your email address will not be published. Required fields are marked *

*


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>