Loading ...
Sorry, an error occurred while loading the content.

292521Re: postfix and Berkeley DB

Expand Messages
  • Sahil Tandon
    Apr 11, 2013
      On Thu, 2013-04-11 at 16:35:28 -0600, LuKreme wrote:

      > # ldd /usr/local/libexec/postfix/smtpd
      > /usr/local/libexec/postfix/smtpd:
      > libmysqlclient.so.16 => /usr/local/lib/mysql/libmysqlclient.so.16 (0x280cf000)
      > libz.so.3 => /lib/libz.so.3 (0x28139000)
      > libm.so.4 => /lib/libm.so.4 (0x2814a000)
      > libssl.so.7 => /usr/local/lib/libssl.so.7 (0x28160000)
      > libcrypto.so.7 => /usr/local/lib/libcrypto.so.7 (0x281ad000)
      > libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x2830a000)
      > libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28321000)
      > libc.so.6 => /lib/libc.so.6 (0x28354000)
      > libcrypt.so.3 => /lib/libcrypt.so.3 (0x2843b000)

      So, you did not explicitly link against a non-default DB library.

      > # file /etc/postfix/virtual.db
      > /etc/postfix/virtual.db: Berkeley DB 1.85 (Hash, version 2, native byte-order)
      >
      > So, postfix appears to be using Berkeley DB but is not linked against it?

      As documented, Postfix uses the default Berkeley DB version that ships
      with your system, which I am assuming is FreeBSD. You can alter this
      behavior by explicitly linking against a different, non-default DB
      version, which would then appear in ldd(1) output. Or, you can disable
      Berkeley DB support entirely by including -DNO_DB in CCARGS.

      --
      Sahil Tandon
    • Show all 9 messages in this topic