Hi, I have tried the latest aspseek 1.2.5. Compared to 1.2.4a it looks better, but there are some strange problems related to resolver and alarm handling. In 1.2.4 I have indexed with "-N 100". The same in 1.2.5 produces huge number of "Waiting for resolver" messages, which disappear with "-R 100". This would still be OK but when index receives an alarm to stop ( -n option or kill -2 ), some of the threads end, while the others do not even after an hour of waiting to finish. Several additional kills might or might not end few more threads. Is there any hint where to look for the problem? kill -9 still stops the index... My system is dual RH7.1, 1GB memory, RH 2.4.2 enterprise kernel, while mysql is on another host. I have tried glibc 2.2.4 with the same result... Best regards, Andrej -- _____________________________________________________________ Andrej Filipcic, E-mail: [EMAIL PROTECTED] Department of Experimental High Energy Physics - F9 Jozef Stefan Institute, Jamova 39, P.o.Box 3000 SI-1001 Ljubljana, Slovenia Tel.: +386-1-477-3674 Fax: +386-1-425-7074 -------------------------------------------------------------
