Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!rice!sun-spots-request From: nao@cuatro.bellcore.com (Neil Ostroff) Newsgroups: comp.sys.sun Subject: Re: Bad YP handling Keywords: Networks Message-ID: <3873@brazos.Rice.edu> Date: 11 Dec 89 16:46:41 GMT Sender: root@rice.edu Organization: Sun-Spots Lines: 28 Approved: Sun-Spots@rice.edu X-Refs: Original: v8n213 X-Sun-Spots-Digest: Volume 8, Issue 221, message 1 of 10 In article <3495@brazos.Rice.edu> Steven V. Christensen writes: >Situation: When I run "make all" in /var/yp on the Sun to re-make and >redistribute the YP databases, it says (for example): > >updated passwd > >yp server not registered at . > >yp server not registered at . >pushed passwd This occurs when 's ypserv(8) is not running. Most likely, you either have a yp configuration problem on the Sun or is not set up to be a slave server. To figure out what's going on, you need to know whether is supposed to be a yp slave server or just a yp client (the Sun is the yp master server). Now verify your Sun yp configuration by cd-ing to /var/yp/your_domain and typing: "/usr/etc/yp/makedbm -u ypservers". If it returns the name of , then your Sun wants to be a yp slave server. Unconfiguring your Sun is somewhat of a pain, however the procedure is described in Chapter 14 of the System and Network Administration manual. If you want to be a slave server, then it needs to be set up. Neil Ostroff Bell Communications Research | UUCP: bcr!nao 100 Schultz Dr. NVC-5J443 | ARPA: nao@cuatro.bellcore.com Red Bank, NJ 07701 | PHONE: (201) 758-5741