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.
As mentioned in another of my recent posts, I have set up a small network for my job, in which I am utilizing 4 Servers running Ubuntu 9.04 Jaunty Jackalope Gnome GUI and Ubuntu Server running underneath (yes I need a GUI for what I am doing).
However, I am having a problem when bringing Ubuntu out of "locked" state, and any time that I am required to authenticate (i.e. sudo bash). After I type in my password, everything hangs for a good 3+ minutes.
To test this, I disconnected the Ubuntu Servers from the network, and I tried to authenticate again. With the server off the network, authentication did not hang, and the GUI came up in seconds. Also, I checked my syslog and memory utilization and both are well within acceptable range that they would not be causing sluggish performance.
With all of this said, I believe that there is some kind of resolution going on when trying to authenticate while the servers are connected to the network (i.e. Kind of like how doing a traceroute in a cmd prompt in Windows without the "-d" takes forever because of name resolution checking).
I should also mention that my network DOES NOT have an internet connection by design.