Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mintaka!think.com!spool.mu.edu!sdd.hp.com!caen!uwm.edu!ux1.cso.uiuc.edu!aries.scs.uiuc.edu!sandrock From: sandrock@aries.scs.uiuc.edu (Mark T. Sandrock) Newsgroups: comp.sys.mips Subject: Re: MIPS NIS Message-ID: Date: 31 Jan 91 19:42:24 GMT References: <1991Jan25.225242.14654@tandem.com> Sender: news@ux1.cso.uiuc.edu (News) Organization: University of Illinois at Urbana Lines: 25 scott@DSG.Tandem.COM (Scott Hazen Mueller) writes: >The material in the 'RISC/os System Administrator's Guide, Volume I' that >discusses NIS is spectacularly useless with respect to *exactly* how and when >you invoke ypbind in the startup process, so I'm not even confident I'm >starting ypbind correctly, though it strikes me as being particularly hard >to screw this up. Check section 3.15 of the RISCos 4.51 Release Notes: Starting NIS "NIS must be started before the automounter and after the portmapper. This suggests that the proper place is a file called /etc/rc2.d/S38nis_local..." They go on to provide a sample startup file for NIS (which does not include yppasswdd nor rpc.passwd, BTW, but we added rpc.passwd to our own version). We have been running NIS under 4.51 for a good month now without problem. Hope this helps. Mark Sandrock -- BITNET: sandrock@uiucscs Univ. of Illinois at Urbana-Champaign Internet: sandrock@aries.scs.uiuc.edu Chemical Sciences Computing Services Voice: 217-244-0561 505 S. Mathews Ave., Urbana, IL 61801 "...make every effort to supplement your ...virtue with knowledge" 2 Peter 1:5