From owner-freebsd-questions Sat Feb 20 19: 8:15 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id E433910E05 for ; Sat, 20 Feb 1999 19:08:06 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.8.8/8.8.8) id WAA15912; Sat, 20 Feb 1999 22:09:41 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199902210309.WAA15912@cc942873-a.ewndsr1.nj.home.com> Subject: Re: NIS In-Reply-To: from Jeroen Ruigrok/Asmodai at "Feb 20, 99 11:59:01 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Sat, 20 Feb 1999 22:09:41 -0500 (EST) Cc: cjclark@home.com, questions@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote, > On 20-Feb-99 Crist J. Clark wrote: > > Jeroen Ruigrok/Asmodai wrote, > >> what could cause rpc.yppasswdd to `hang' at boot up? And with hang I > >> mean it seems to need to time out on something. > > > > Is the machine a master server, slave server, or client? > > A server, master, else I wouldn't be running yppasswdd I guess ;) Just making sure. > FreeBSD daemon.ninth-circle.org 4.0-CURRENT FreeBSD 4.0-CURRENT #12: Sun > Feb 14 19:24:39 CET 1999 > asmodai@daemon.ninth-circle.org:/work/FreeBSD/src/sys/compile/DAEMON i386 > > [asmodai@daemon] (24) $ grep ^nis rc.conf > nisdomainname="ninth-circle" # Set to NIS domain if using NIS (or NO). > nis_client_enable="NO" # We're an NIS client (or NO). > nis_client_flags="" # Flags to ypbind (if enabled). The server is not a client to itself? > nis_ypset_enable="NO" # Run ypset at boot time (or NO). > nis_ypset_flags="" # Flags to ypset (if enabled). > nis_server_enable="YES" # We're an NIS server (or NO). > nis_server_flags="" # Flags to ypserv (if enabled). > nis_ypxfrd_enable="NO" # Run rpc.ypxfrd at boot time (or NO). > nis_ypxfrd_flags="" # Flags to rpc.ypxfrd (if enabled). > nis_yppasswdd_enable="YES" # Run rpc.yppasswdd at boot time (or NO). > nis_yppasswdd_flags="-t /var/yp/master.passwd -v" # Flags to rpc.yppasswdd (if enabled). ^^ This is good. Do you get any info? Perhaps I should have asked initially, why do you think that yppasswdd is hanging in the first place? > So we also need an ll from /var/yp: > > [asmodai@daemon] (29) $ ll > total 43 > 1 drwxr-xr-x 3 root wheel - 512 Feb 20 23:49 ./ > 1 drwxr-xr-x 19 root wheel - 512 Dec 30 23:18 ../ > 18 -r--r--r-- 1 root wheel - 18126 Feb 16 20:23 Makefile > 18 -r--r--r-- 1 root wheel - 18126 Feb 15 02:29 Makefile.dist > 2 -rw------- 1 root wheel - 1249 Feb 20 13:17 master.passwd > 1 drwxr-xr-x 2 root wheel - 512 Feb 20 13:17 ninth-circle/ > 2 -rw-r--r-- 1 root wheel - 1064 Feb 20 13:17 passwd > 0 -rw-r--r-- 1 root wheel - 0 Feb 16 20:41 ypservers > > ypservers is empty since there's only one server, Does the master need to have itself listed in ypservers? > master.passwd is a > changed version of the /etc one. > > All the NIS maps got created as they should I think. What still confuses me > is that from the tutorials I managed to overview, some mention to add > +::::::::: or +::: to the /var/yp/master.passwd and /etc/group files. Those lines need to be added to /etc/master.passwd and /etc/group on the _clients._ -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message