From owner-freebsd-questions@FreeBSD.ORG Sun Aug 3 21:19:31 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACF6537B401 for ; Sun, 3 Aug 2003 21:19:31 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AF1243F85 for ; Sun, 3 Aug 2003 21:19:31 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h744JU9V084951; Sun, 3 Aug 2003 23:19:30 -0500 (CDT) (envelope-from dan) Date: Sun, 3 Aug 2003 23:19:30 -0500 From: Dan Nelson To: Jin Guojun Message-ID: <20030804041930.GJ38843@dan.emsphone.com> References: <200308040411.h744BePX067732@portnoy.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308040411.h744BePX067732@portnoy.lbl.gov> X-OS: FreeBSD 5.1-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: freebsd-questions@freebsd.org Subject: Re: pw_mkdb() failed in rpc.yppasswdd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 04:19:32 -0000 In the last episode (Aug 03), Jin Guojun said: > When using yppasswd to change a user password, rcp.yppasswdd failed in two ways: > > change passwd from root on NIS server: > ------- server syslog messages --------- > passwd: in pam_sm_chauthtok(): yppasswd_local(): failed to connect to rpc.yppasswdd: > nis.server.$DOMAIN: RPC: Program not registered > > change passwd from a user on either NIS server or a remote machine: > ------- server syslog messages --------- > rpc.yppasswdd[349]: pw_mkdb() failed > passwd: in pam_sm_chauthtok(): yppasswd_remote(): NIS password update failed > > ========= end of messages ========= > > This is on 5.1 release. What would be the problem? I believe both bugs have been fixed in -current. Updating the sources to rpc.yppasswd and rebuilding it should work, if you don't want to update the entire system. -- Dan Nelson dnelson@allantgroup.com