From owner-freebsd-ports@FreeBSD.ORG Wed Jun 1 22:01:42 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88B3E16A41F for ; Wed, 1 Jun 2005 22:01:42 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id F288543D49 for ; Wed, 1 Jun 2005 22:01:41 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so20933wri for ; Wed, 01 Jun 2005 15:01:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MvtN+2O+dTa3CKHu9LjJxS7toix6IhFIwQ+WZBRcDV1fx2718+OTcQv9KpHvCaHqEXrjz3JwAGgrr47VQsbnYhu31/gAypKn+vuHBt3du2RbYKXT2JrAtWBPix4/iSGYcvleUApXG4NauPHPJ3ESEzEtQY+5DlHb6o8ZOWUXEVk= Received: by 10.54.39.69 with SMTP id m69mr145616wrm; Wed, 01 Jun 2005 15:01:40 -0700 (PDT) Received: by 10.54.29.77 with HTTP; Wed, 1 Jun 2005 15:01:40 -0700 (PDT) Message-ID: <790a9fff050601150173d7bd34@mail.gmail.com> Date: Wed, 1 Jun 2005 17:01:40 -0500 From: Scot Hetzel To: Mark Edwards In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: ports@freebsd.org Subject: Re: FreeBSD Port: cyrus-sasl-2.1.21 -- Couldn't update db X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Scot Hetzel List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 22:01:42 -0000 On 5/30/05, Mark Edwards wrote: > When I use saslpasswd2 to set or change a password, I always get a log > item saying that saslpasswd2 "Coudn't update db" even though the > password is changed successfully, the db file is modified, and > subsequent authentication with the new password succeeds just fine. >=20 > An example: >=20 > May 30 03:46:13 lilbuddy saslpasswd2: setpass succeeded for > cyrus@mail.antsclimbtree.com > May 30 03:46:13 lilbuddy saslpasswd2: Couldn't update db >=20 Been a while since I used the cyrus-sasl ports, but when I was updating them, I had added to pkg-install: echo "test" | ${PKG_PREFIX}/sbin/saslpasswd2 -p -c ${CYRUS_USER} ${PKG_PREFIX}/sbin/saslpasswd2 -d ${CYRUS_USER} It would issue a warning, but still create a blank sasldb file. Then as you add new users to the sasldb file, it shouldn't give you any further warnings. NOTE: If you install with BATCH=3Dyes, then pkg-install will not create the blank sasldb file, and you will get a warning on the first user added. Does the warning occur with the first user added (no previous sasldb/sasldb2 file) or with every additional user added? Scot