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

[WK]

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