Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
LDAP's one of these things I keep meaning to get into but never get further with than creating a bunch of basic accounts, that's it, I keep meaning to do more with it such as configuring it for use on my wireless network.
What I want to do is this:
Create and user account but with specific information to attributes, for example, instead of just one loginShell have 3 loginShell's
The idea being I want to have eventually 3 groups of servers where I can have different user configurations, for example a group of servers where some users only have a chrooted environment, and can give them different passwords for these environments, but without having to create a different subtree and duplicate a lot of the information and effort maintaining.
I'm reluctant to create a custom schema and then map the custom attribute on the client as I don't want to come into conflict with any other schema's I may use in future. Because I've not done much with ldap I'm hoping that there's something I've overlooked or a function not often covered that might achieve this.