Hi Sebastien, Sebastien Roy pÃÅ¡e v st 12. 11. 2008 v 16:08 -0500: > On Wed, 2008-11-12 at 13:02 -0800, Stephen Hahn wrote: > > * Dan Mick <[EMAIL PROTECTED]> [2008-11-12 20:46]: > > > I have to believe there's more to it than that; surely I have to svcadm > > > as > > > Milan notes, and then I have to do some > > > selection of domain, and potentially servers, etc. I recall some > > > nonsense > > > about manually creating directories in /var/yp, etc. that NIS experts > > > just > > > rattle off, but that I've never done manually. > > > > ypinit -c will ask you the questions, set the appropriate files, > > create directories, and enable services. (Turning a NIS client with an > > explicit list of servers into a broadcast client requires the fiddling > > you mention.) > > Minor nit: Actually, ypinit -c won't run until you've set the default > NIS domain for the system by running "domainname <bla>" and populating > the /etc/defaultdomain file. > > In addition to that, if what you want is to simply broadcast for a local > server (which is probably the safest way to run a NIS client given that > IT keeps changing the IP addresses and/or names of the NIS servers on a > daily basis), ypinit won't let you do that. You need to set your > domainname as above, create an empty /var/yp/binding/<domainname> > directory, and "svcadm enable nis/client". > > This is a mess, and one that will hopefully be remedied in NWAM Phase 1. >
I don't think so. Not without project Duckwater. NIS/LDAP client setup is small nightmare for newbies. But who needs it? Best regards, Milan
_______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
