Hi Torsten, I recently concluded another series of tests with the slapd and it seems my problems have vanished. I will now include the dependencies (had to learn that one first). I am now testing on a development station on which normally after a couple of hours the machine would lock up. This did not happen so far. The only difference is that I used the dpkg-reconfigue to install a brand new ldap database + slapd.conf and imported my own ldap data using the ldif format. So making this ascii step in between the upgrading might make a difference. It could be an idea that anyone who has problems with slapd, follows this process because at least this eliminates the problem of old binary databases. I will keep slapd running on the dev machine and if the problem does not come back, I will try a production machine (an hold my breath). So far so good. When the problem comes back, I will make a new bug report because I now have the feeling that my problem had nothing to do with this thread. Also the problem with the IPv6 kernel module has vanished. So I hereby withdraw all my comments. gr. Robert Ps I might have some suggestions for the text used in the dpkg-reconfigure script, are you interested?
Version: 2.2.26-3 Depends: libc6 (>= 2.3.2.ds1-21), libdb4.2, libiodbc2 (>= 3.52.2), libldap-2.2-7, libltdl3 (>= 1.5.2-2), libperl5.8 (>= 5.8.7), libsasl2 (>= 2.1.19), libslp1, libssl0.9.7, libwrap0, coreutils (>= 4.5.1-1) | fileutils (>= 4.0i-1), psmisc, libldap-2.2-7 (= 2.2.26-3), perl (> 5.8.0) | libmime-base64-perl PreDepends: debconf (>= 0.5) Recommends: db4.2-util, libsasl2-modules Suggests: ldap-utils Conflicts: umich-ldapd, ldap-server, libbind-dev, bind-dev, libltdl3 (= 1.5.4-1) Replaces: libldap2, ldap-utils (< 2.2.23-3) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
