From owner-freebsd-current Fri Nov 1 12:45: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D194037B401; Fri, 1 Nov 2002 12:45:00 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68FDA43E42; Fri, 1 Nov 2002 12:44:58 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id gA1KauOo037203; Fri, 1 Nov 2002 15:36:56 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Nov 2002 15:36:56 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Baldwin Cc: current@FreeBSD.org Subject: Re: ypbind doesn't work right on freshly installed machines In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Per our discussion out-of-band, and just for the reference of others who might have the same question, forced dependencies for rpcbind from ypserv and ypbind aren't present right now, you can work around by explicitly enabling rpcbind in rc.conf. You might actually see rpcbind running later in boot, but it's from another forced dependency that is present. The symptom of this is that ypbind silently fails if the RPC port mapper isn't present :-(. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories On Fri, 1 Nov 2002, John Baldwin wrote: > I installed two machines with fresh current snapshots last night > and this morning. One was an i386 box the other a sparc64 box. > Both machines are NIS clients from the same server. I do have > other 5.x and 4.x boxes on the same LAN at home that also are NIS > clients of the same server (the server is 4.7 box). All my other > machines work fine. However, for the two freshly installed > test boxs, ypbind doesn't find a server the first time it is run > during /etc/rc startup. If I login as root and run 'ypbind' again > then it works fine. All my other 5.x boxes which are not fresh > installs do not have this problem. Anyone have any ideas? > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message