On Thu, Mar 29, 2001 at 11:01:11PM +0200, Olaf Zaplinski wrote:
> Hi all,
>
> I have 2 Linux machines, they are almost identical:
>
> Kernel 2.2.18
> cyrus-imapd-2.0.12
> cyrus-sasl-1.5.24
> Berkeley DB 3.1.17
> openssl-0.9.6
> sendmail 8.11.3
>
> One is a SuSE 7.1 distro, the Berkeley DB and openssl came as a RPMs; the
> other one is a Debian 2.2, and it was hard work to get Berkeley DB compiled
> and installed.
If you're using the unstable distro (or testing), they've now got a DB3
package out. Sometime last week, I believe.
> On the SuSE box, I did not much more than compiling and installing
> everything, and its cyrus imapd still works fine.
>
> On the Debian box I spent a lot of time on the Berkeley DB because several
> packages did not regognize it, or they segfault'ed when starting, but they
> do now except for imapd.
> Today I compiled everything needed and linked it against the Berkeley DB:
> sasl, sendmail and imapd. But now, whenever I start 'master', I get a
> segmentation fault.
Make sure that you're actually linking agains the DB3 libraries -- if the DB2
libraries are kicking around, it'll link against that. Do this for SASL,
sendmail, and cyrus.
> Any ideas? I don't know how to proceed and am about to cancel that imap
> server project.
>
> I *really* would love to fdisk that *&%!@ Debian box and install SuSE, but
> my boss says no, although I spent more than 4 times the time I spent on the
> SuSE box to have imapd up and running, and I am not finished yet.
>
> Could it be that some parts (libs?) of the Debian distribution are simply
> outdated? From time to time I find .deb packaged software which is
> significantly more outdated than the packages of other distros.
Yep, that's a large problem with Debian. You can try contacting the maintaner
of the package to see what's up.
