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.
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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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:
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!
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.