Date: Thu, 02 Jun 2005 21:10:30 +0900 From: Hajimu UMEMOTO <ume@freebsd.org> To: Mark Edwards <mark@antsclimbtree.com> Cc: ports@freebsd.org, Scot Hetzel <swhetzel@gmail.com> Subject: Re: FreeBSD Port: cyrus-sasl-2.1.21 -- Couldn't update db Message-ID: <yge64wx9cy1.wl%ume@mahoroba.org> In-Reply-To: <94f6a6f4db839f65d907d729e14a15ad@antsclimbtree.com> References: <e3da8d252adb98ba8f33d12218e011c5@antsclimbtree.com> <790a9fff050601150173d7bd34@mail.gmail.com> <94f6a6f4db839f65d907d729e14a15ad@antsclimbtree.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
>>>>> On Thu, 2 Jun 2005 12:17:19 +0200
>>>>> Mark Edwards <mark@antsclimbtree.com> said:
mark> It occurs every time saslpasswd2 updates the db. The db is
mark> successfully updated, but there is a warning issued. When saslauthd
mark> updates the db, no warning.
mark> I also get the following non-sensical warnings in /var/log/auth.log:
mark> Jun 2 02:03:49 lilbuddy imaps[61325]: no user in db
mark> Jun 2 02:18:30 lilbuddy exim: no user in db
You can simply ignore the messages. You can see following chunk in
saslpasswd.c:
/* Either we were setting and succeeded or we were disabling and
failed. In either case, we want to wipe old entries */
/* Delete the possibly old entries */
/* We don't care if these fail */
propctx = prop_new(0);
if (!propctx) ret = SASL_FAIL;
if (!ret) ret = prop_request(propctx, delete_request);
if (!ret) {
ret = prop_set(propctx, "cmusaslsecretCRAM-MD5", NULL, 0);
ret = prop_set(propctx, "cmusaslsecretDIGEST-MD5", NULL, 0);
ret = prop_set(propctx, "cmusaslsecretPLAIN", NULL, 0);
ret = sasl_auxprop_store(conn, propctx, userid);
}
if (propctx) prop_dispose(&propctx);
The messages are out by this compatibility craft.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?yge64wx9cy1.wl%ume>