Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
In our cluster of RedHat4 & 5 machines, if someone locks the computer and walks away no body can use it. Is there a feature in RedHat5, Gnome, KDE etc that would allow for the option of switching users at the lock screen, so more than one person can be logged in?
Isn't the point of locking a machine to prevent others from accessing it?
They don't have root so if it functions like XP their activities are locked while the new user starts a entirely new session.
The users lock the PCs because they are running simulations that take some time to complete. So if all 20 or pcs are running day long simulations the room can't be used for new runs until one finishes.
I've done a fair amount of searching for a solution to your problem; I've found that Fedora supports enabling "Switch User" on the lock screen; but there doesn't seem to be a similar way to do it in RHEL.
If any of the other member's have a solution they can perhaps help you.
As an aside can your students simulations be started via the command line?
If so, you could let them shell into a screen and kick off a simulation; and detach without killing that process - in that way other users can still login to the GUI.
Also; take into account that allowing those "simulations" to run in parallel with someone doing miscellaneous actions on the box; can result in the resources being exhausted; and thus simulation data being lost due to a crash etc.
In another forum I found this solutions that fixed the problem for me:
1. CTRL ALT F1-12
2. Goes to login prompt -> login
3. startx -- :1 7 most likely already in use but the gui you just dropped out of.
That can be controlled by starting login prompts on
all console terminals, leaving ONLY the unused ones (1/2/3...) available for usenwith X. I believe the default number of console terminals is 12, so assuming that, I have:
F1 - available for X by default
F2-6 -login terminals
F7-12 available for X
To configure the login terminals cd into /etc/event.d. The files tty1-6 are the existing definitions, so 0,7,8,9,10,11 can be defined. If tty7-10 are created (just copy tty1, and change the references to tty1 to the tty7-10 being created)that will allow only two X servers to exist - one for tty0 (F1), and one for tty11 (F12)
The above solution is not for the question you originally asked about enabling the "Switch User" button. The above switches between run levels and allows rc 3 login - which is a different question altogether.
I did ask for a "feature" that resulted in the ability to switch user. The solution I posted addresses the title, "Switch User at screen lock". I posted it for any one else out there that may be looking for the same thing. If you are using Fedora, it has a switch user feature built-in.
I'm open to suggestions for a new title to the thread if you think it would be helpful.
Don't get me wrong - its a good thing that you posted your solution.
But the thing is, your solution is not for "Switching" users. When you "Switch" users the implication is that the box is under the control of a different user; and only that user ala Windows.
But in Linux terms; what your solution does is initialize a different Red Hat run level; and allows a shell login to the box. This could have been achieved without even being in front of the machine itself - that is you could have used a shell client on any machine that is allowed to connect to the RHEL machine in question; and login to the box.
Thanks for the clarification. It actually gives me another question, terminals. I know MS has terminal servers and you have thin clients connecting to the terminal server. I would imagine Linux can more than do the same thing. Now I guess I'm on the search for a thin client.
I'm not sure what the correct terminology is. I was thinking of a few "dummy" terminals or cheap boxes that connect to a more robust machine. The dummy terminals would just be strong enough to connect over the network and pipe back the desktop. Basically a little box, keyboard and mouse.