This Webmin module on the other hand updates the files on each client system so that users and groups remain synchronized. And because clients must frequently query the server, it does not work as well over a slow network. If the master server goes or network goes down, client systems will be unable to look up user information, causing logins and many programs to hang. NIS works well and is easily configured from within Webmin, but has some down sides. ![]() NIS client systems query a master server for information as well as reading their /etc/passwd and /etc/group files, which makes the accounts available on all clients. ![]() There is a widely available and more commonly used method of managing users, groups and other services across multiple machines though NIS, covered in NIS Client and Server. Using this module is far easier than manually creating an account on each system. If you have a large number of hosts on your network and want people to be able to login to all of them, some mechanism is needed for creating Unix accounts on each system. This module allows you to manage Unix users and groups only multiple systems from a single interface. You should also read chapter 4 which covers the Users and Groups module, as many of the forms and pages in the Cluster Users and Groups module are similar to that one. All of the cluster-related modules (this one, Cluster Software Packages and Cluster Webmin Configuration) make use of the Webmin Servers Index module and RPC to control other systems. ![]() Before reading this chapter you should be familiar with Webmin's cluster management capabilities, explained in the introduction to Cluster Software Packages.
0 Comments
Leave a Reply. |