Red HatThis forum is for the discussion of Red Hat Linux.
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 try to set up a Linux box, that handles LAN accounts and supports roaming profiles. But after a several day, I think, I am in lack of some basic knowledge...
What I did:
A LDAP-server is up and running, users are added via webmin. Webmin uses the smbldap-scripts to configure users.
Both, client and server, are set to find user data via LDAP and autheticate via LDAP. I did this setting via "authconfig".
What I get:
I can login to the client via su xxx, assuming, that xxx is a user provided by the server and xxx is not saved as local user on the client.
But I can't login to the clients initial authentication screen (the mask, that welcomes me after booting the client). Not even with user xxx. This screen accepts only local saved users. Do there work different authentication procedures?
I noticed that there is a little latency between hitting <enter> and the authentication-failure message on the main login screen.
This latency lasts shorter, if I use server-saved users. If I type something completely unknown into the mask, the latency lasts longer.
But both cases result in the same "unknown user or password" screen.
Does anybody know this symptomathics? Or is LDAP not the way to reach the goal?
I searched for some general Linux-authentication reading, but didn't find some basic stuff. I am just a few weeks into the Linux world...
A long posting... Thanks for reading!
And, in advance, thanks for any hint!
Clemens von Musil
... finally I found the issue. Following happened:
The client system did login correct, but didn't find ~. I wanted to manage the home-sharing-issue after the login thing.
Graphical login siad nothing about the homedir as mentioned above, the commandline login pointed me the right direction.