[Beowulf] Fwd: NIS limitations question
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
DGS dgs at gs.washington.eduThu Feb 9 11:05:28 PST 2006
- Previous message: [Beowulf] Fwd: NIS limitations question
- Next message: [Beowulf] Fwd: NIS limitations question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Feb 09, 2006 at 12:17:43PM -0500, Mark Hahn wrote: > > > > I belive i have seen on this maling list*, and other internet fourms** some > > > > limitation of NIS, but i have failed to find a documented limiation from > > > > SUN, or from the various linux distrubutions, did any one try to research > > > > the scalability of NIS servers? > > > > > > The standard answer, if you only rarely push, is to make every client > > > a slave. > > > > The less violent solution is to simply run nscd (name service caching > > daemon) on all clients - that will take a lot of the load off of both > > your NIS and DNS servers :) > > I have deep admiration for DNS, and quite a lot of scorn for > various other systems that try to do similar things, poorly. > for instance, LDAP works, but that's the best you can say for it. > imagine if the LDAP folk had thought of how to use DNS as a > directory infrastructure (but alas, they were x500 recidivists ;) The Rocks Linux toolkit comes with a name service called "411". It seems to be a mechanism for distributing password, group and other such files to a cluster's nodes. I've never used it. Anybody care to comment on how well it works? David S. >
- Previous message: [Beowulf] Fwd: NIS limitations question
- Next message: [Beowulf] Fwd: NIS limitations question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
