From owner-freebsd-stable Thu Aug 8 4:14:43 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9869E37B400 for ; Thu, 8 Aug 2002 04:14:42 -0700 (PDT) Received: from relay02.cablecom.net (relay02.cablecom.net [62.2.33.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9468F43E81 for ; Thu, 8 Aug 2002 04:14:41 -0700 (PDT) (envelope-from hanspeter_roth@hotmail.com) Received: from gicco.cablecom.ch (dclient217-162-157-104.hispeed.ch [217.162.157.104]) by relay02.cablecom.net (8.11.6/8.11.4/SOL/AWF/MXRELAY/06072001) with ESMTP id g78BEeZ65782 for ; Thu, 8 Aug 2002 13:14:40 +0200 (CEST) Received: (from idefix@localhost) by gicco.cablecom.ch (8.11.6/8.11.6) id g78BEe001672 for freebsd-stable@FreeBSD.ORG; Thu, 8 Aug 2002 13:14:40 +0200 (CEST) (envelope-from hanspeter_roth@hotmail.com) Date: Thu, 8 Aug 2002 13:14:40 +0200 From: Hanspeter Roth To: freebsd-stable@FreeBSD.ORG Subject: Re: NIS fails after upgrade to 4.6 Message-ID: <20020808131440.F477@gicco.cablecom.ch> Reply-To: freebsd-stable@FreeBSD.ORG Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from dsilver@urchin.com on Mon, Aug 05, 2002 at 09:44:31AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Aug 05 at 09:44, Doug Silver spoke: > After upgrading a 4.4-STABLE machine to 4.6-STABLE, NIS is not > working. The NIS master is a solaris box, however nothing else has Could it have something to do with lib*crypt* links? Mine seem to be set anew at last update: lrwxr-xr-x 1 root wheel 13 Aug 3 20:32 /usr/lib/libcrypt.so -> libcrypt.so.2 lrwxr-xr-x 1 root wheel 14 Aug 3 20:38 /usr/lib/libcrypto.so -> libcrypto.so.2 -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message