the unable to open Berkeley db /etc/sasldb2: No such file or directory issue

[WK]

and thanks again.

I'm collecting quite a list of these little tidbits. All very minor 
issues like the ('/iRony/') fix.

I should maybe put them into bug ticket for the devs to knock out when 
they are bored

-bill

On 1/7/2014 5:33 PM, Geoff Nordli wrote:
> On 14-01-07 03:47 PM, WK wrote:
>> So we have this problem in our logs as well.
>>
>> As described below, this is on a fully functional Kolab 3.1 install 
>> that was done on a fresh minimal CentOS 6.5 VM. NOTHING is broken on 
>> this server, its just annoying to see those errors in the logs.
>>
>> So I google around and I found this:
>>
>> http://www.marshut.com/xuzwh/unable-to-open-berkeley-db-no-such-file-or-directory.html 
>>
>>
>> The poster Geoff Nordli describes the problem and then at the bottom 
>> he says "Thanks Chris" for the fix.
>>
>> What was the fix? I've been all over marshut and can't find what the 
>> response was that fixed Geoff's issue.
>>
>> Are Geoff or Chris on this list <grin>
>>
>> -bill
>
> Hi Bill.
>
> http://lists.kolab.org/pipermail/users/2013-October/015626.html
>
> Create a dummy file with:
>
> saslpasswd2 sasldb2
>
> Geoff
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users