I found Ben's poll interesting: http://www.cuddletech.com/blog/pivot/entry.php?id=1094
although I would have to step back a pace and ask - "What Naming Service"? Because it's not entirely obvious to me that a directory server is an optimal answer (it may be the best, but I don't find it optimal). Now I've used standard Name SErvices - NIS and NIS+ - extensively, and have done a lot of work on LDAP. NIS: Pretty easy to set up, limited functionality beyond the basic, data management facilities are crude, scales poorly. NIS+: A reputation for difficulty, although that's not really true (although it once was); easy to set up and manage once you know what you're doing. Decent functionality, scales well, data management facilities are excellent, limited interoperability, no future. LDAP: More demanding of resources. While LDAP itself is easy to set up, actually configuring it to work correctly is a bear. Scales well, excellent interoperability, but data management facilities are primitive to non-existent. In the past I've loved NIS+ due to its excellent data management facilities (basically, you can query/modify any field with complete API and CLI control). So I'm spending more time with LDAP, and I'm hating it. Sure, I can generate LDIF and feed it in, but it seems such a kludge, and correct configuration seems far too difficult. For starters, is there a complete and accurate guide to setting up (say) OpenDS and configuring it as a Solaris nameservice (because I haven't found anything even remotely helpful or accurate). And then, how do people manage data inside LDAP? Is writing your own LDIF really the answer? -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ _______________________________________________ sysadmin-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
