Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I recently posted to this site and had hardware issues to resolve with a lost hard drive and a corrupt boot loader. I'm back on line now. On the prior post I loaded realvnc, found some difficulties, removed it and have now loaded tightvnc. I must login to the redhat server to enable vnc access from my remote machine. I would like to have tightvnc start at boot.
I see all of the files installed thru rpm -ql tightvnc-server and all look good. I have changed the /etc/sysconfig/vncservers to include the line VNCSERVERS="1:myloginname". After a reboot, it still will not start automatically during boot.
I've also tried, after a login, to use the following commands:
chkconfig vncserver on
...and both start fine. After yet another reboot, the vnc service will not start.
From the server gui I can see the vncserver is started with Xvnc running on pid 4906.
I think I'm missing something minor, but have failed to put my fingers on it. Any help would be appreciated.
Well, this is a total hack (not the right way to do it, but it should work), but you could simply add '/etc/init.d/vncserver start' to your rc.local file (it's the last startup script that runs after everything else has loaded).