(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version



Detailed procedure for installation of VNC on OpenServer

March 2004 By Lytle David Smith


Lytle David Smith
1421 Lexington Road
Louisville, Kentucky  40206
Voice: (502) 561-1111
Fax: (502) 231-9215
E-mail: Home@ComputerLandInc.com
http://david.computerlandinc.com/





I've been working hard to get VNC working on OpenServer 5.0.6. In doing so, I have written these Bourne shell scripts to automate the process of downloading, extracting, installing and configuring the binaries for tightvnc and all of the packages on which it depends.

Apparently there are some issues with having the VNC Java client work in conjunction with inetd. The "5_configure" script will prompt you to choose between the Java client and inetd. It appears to be because when an attempt is made to connect to port 58XX, thus initiating a download of the Java client, VNC is not actually running at that point. It doesn't get launched until after the Java client is already downloaded and executing.

I tried embedding the Java client into a web page, but I couldn't get it to work. The Java client would download and prompt for a password, but then it would report an error, "java.io.EOFException".

If you choose the Java client, you will be prompted to select a VNC password that must be used by the operator to connect to VNC, but the operator will not be required to login once connected, and they will be logged-in as root. If anyone can tell me how to configure TightVNC to prompt for a login when launched at boot-time, then perhaps I can modify the script to do that. I tried changing "scosession" to "scologin" in /.vnc/xstartup, but it wouldn't work that way.

If you choose inetd, VNC will allow connections without a password, but the operator will be presented with a login prompt with which they can login as any user. If anyone can tell me where TightVNC stores the password when launched by inetd, then perhaps I can modify the script to utilize it. It isn't under /.vnc. I think that's because inetd is starting Xvnc with NOLUID, so it doesn't look in /.vnc, which is root's home directory.

Below are the scripts that I used to download, extract, install and configure tightvnc on OpenServer Enterprise 5.0.6. I have divided the process into five separate scripts, because I wanted to be able to repeat certain sections without repeating the entire process.



1_download
Download TightVNC, Glib, Bash, and Perl to /usr/local/media.

2_extract
Extract downloaded media.

3_installdependencies
Uninstall and reinstall Glib, Bash and Perl.

4_installtightvnc
Uninstall and reinstall TightVNC.

5_configure
Configure TightVNC for either, inetd or Java client.


I hope this saves someone all of the trouble it took me to get this working. Good luck.




More Articles by Lytle David Smith




Click here to add your comments


---November 25, 2004







Fri Apr 17 06:05:00 2009: Subject: VNC   JEGAN

gravatar
I am new to vnc. i have tried two may times to connect vnc but i could't.
how to connect vnc in two computer. can any one advice me please

advance thanks
G.Jegan.



Fri Apr 17 10:10:19 2009: Subject:   TonyLawrence

gravatar
How can we possibly help you? You've given no details as to what you have, what you did, what happened? You need to read http://www.catb.org/~esr/faqs/smart-questions.html

This is NOT the place to ask such questions anyway. See http://aplawrence.com/Forum/questions.html



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



/OSR5/osr5vnc.html copyright March 2004 Lytle David Smith All Rights Reserved

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


book graphic unix and linux troubleshooting guide

My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!



 I sell and support
 Kerio Mail server






More:
       - Access
       - Administration
       - Networking
       - OSR5
       - Remote Acces


Unix/Linux Consultants

Skills Tests

Guest Post Here











My Favorites

Change Congress