Um 21:01 Uhr am 06.04.05 schrieb Torsten Landschoff: > On Wed, Apr 06, 2005 at 03:32:11PM +0200, Sven Hartge wrote:
>>> I thought so as well. Did you use a DB_CONFIG file suited for your >>> setup? >> Yes, of course. >> #txn_checkpoint 128 15 1 >> set_cachesize 0 252428800 0 >> set_lk_max_objects 100000 >> set_lk_max_locks 100000 >> set_lg_regionmax 1048576 >> set_lg_max 8388608 >> set_lg_bsize 2097152 >> set_lg_dir /var/lib/ldap/logs/ >> #set_lk_detect DB_LOCK_DEFAULT >> set_tmp_dir /tmp/ >> #set_flags DB_TXN_NOSYNC >> #set_flags DB_TXN_NOT_DURABLE > Hmm, very interesting. I wonder why it works at Stanford and apparently > nowhere else. I was notified today that putting a DB_CONFIG file into > the directory has no effect after the initial database was created so > I'd like to ask if you did it "in time". Of course. First I copied this DB_CONFIG into /var/lib/ldap, the I de-commented the last two lines, slapadd'ed my data, re-commented the last two lines and fired up slapd. > Sorry for the all problems, I'd really like to have these problems > fixed! Right now I am running with LD_ASSUME_KERNEL=2.4.1 as suggested in $the_other_bug, so far no problems, but as this sched_yield()-problem needs some time to show, I don't know, if this really is the solution or if I am just lucky right now. Grüße, Sven. -- Sven Hartge -- professioneller Unix-Geek und alltime Nerd Meine Gedanken im Netz: http://sven.formvision.de/blog/
