Linux - General This 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. |
| Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
01-01-2007, 08:46 PM
|
#1
|
|
LQ Newbie
Registered: Oct 2006
Distribution: fedora 6, ubuntu
Posts: 16
Rep:
|
setting up "network accounts"
At this point, I have 2 or 3 (k)ubuntu workstations and a linux server in my house. When I upgrade the ubuntus, its a pain to reconfigure the accounts on each computer for each person in my family. How do I set up "network accounts"? I tried looking for a tutorial, but i don't know the technical name for this. I want to make it so i simply configure accounts on the server and each client looks to the server for user authentication/login.
i hope this is clear
thanks
krelp
|
|
|
|
01-01-2007, 10:59 PM
|
#2
|
|
Member
Registered: Jun 2002
Location: Orange County, CA
Distribution: Debian (squeeze), kernel 2.6.30-2-amd64
Posts: 32
Rep:
|
Hi Krelp,
I'm afraid I'm quite short on concrete details, but I think one avenue that will solve your problems is LDAP. I used it about a year or so ago to centralize login authentication to a single server, and got it working on my home network, but I kind of drifted onto other things after that. So you'll have to do a fair amount of reading on the subject to figure out how it'll help your particular situation; to that end, here are some links I found useful:
http://www.enterprisenetworkingplane...le.php/3088441
http://defindit.com/readme_files/ldap.html
http://docs.sun.com/source/816-5616-10/ldap.htm#12978
http://www.openldap.org/doc/admin23/
http://www.zytrax.com/books/ldap/
http://www.linuxdevcenter.com/pub/a/...1/08/ldap.html
http://www.onlamp.com/pub/a/onlamp/2001/08/16/ldap.html
If you're willing to put down money for a book, I can highly recommend this one by Gerald Carter, he really explains it clearly in detail:
http://www.oreilly.com/catalog/ldapsa/index.html
Once I got LDAP running, I was able to create login accounts on the server. Then on client machines you can configure them to refer to the server for authentication. Once authenticated, you can even have a user's /home directories (which reside on the server) mounted on the client after login has completed. This means that any changes a user makes to his/her desktop will follow them should they log in from a different machine on the same network later.
I'm sorry I can't offer more details at this point, like I said, I did this a couple of years ago. But I think it's one solution to your dilemma, and hopefully others on this site will be able to fill in some blanks. Good luck!
|
|
|
|
01-02-2007, 08:48 AM
|
#3
|
|
LQ Newbie
Registered: Aug 2006
Location: Western PA
Distribution: PCLinuxOS 2007
Posts: 16
Rep:
|
One thing you can try is NIS, I think that might be a bit easier to setup rather than LDAP.
Edit: here is the URL to a tutorial on NIS:
http://www.linuxquestions.org/linux/...mation_Service
Last edited by jman623; 01-02-2007 at 08:51 AM.
|
|
|
|
01-02-2007, 09:32 AM
|
#4
|
|
Senior Member
Registered: Nov 2005
Location: Belgium
Distribution: Red Hat, Fedora
Posts: 1,515
Rep:
|
Or look on http://www.tldp.org, under the Networking section for guides & how-tos to set up
LDAP, NIS, or other forms of centralized login.
|
|
|
|
01-02-2007, 10:01 AM
|
#5
|
|
LQ Newbie
Registered: Oct 2006
Distribution: fedora 6, ubuntu
Posts: 16
Original Poster
Rep:
|
thanks
i'll start reading these and see if i can get something set up.
krelp
|
|
|
|
01-02-2007, 01:47 PM
|
#6
|
|
Member
Registered: Sep 2006
Location: Sydney Australia
Distribution: fedora/Ubuntu
Posts: 69
Rep:
|
Password server using rdist
Using NIS and LDAP is a little top heavy for a simple home system. I always feel umeasy with NIS because all its information is stored in unreadable databases.
The command rdist distributes files to remote computers. It uses ssh transfer making it secure and is commonly is used for distributing the passwd, group and shadow files. See
http://www.togaware.com/linux/survivor/Using_rdist.html
and google for the rest
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 10:24 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|