Hi again! I've discovered that searchd mostly goes down when I run the ./index and run an query. If the index-process is finished it's seem to work well. Claus -----Oprindelig meddelelse----- Fra: Claus Jul Larsen [mailto:[EMAIL PROTECTED]] Sendt: 24. april 2001 15:46 Til: '[EMAIL PROTECTED]' Emne: SV: SV: [aseek-users] Re: kill -SIGHUP searchd, re-read searchd. conf? Hi Kir, I've upgraded to 1.1.4 and the result is same. searchd goes down and dump a core file when there are more than one sites indexed. Mostly if I search for test* (test is extract a word with wildcard - maybe it's the reason???) When I search without wildcard it's working well ... When I run searchd -D the dlog file show: Starting search daemon from ASPSeek v.1.1.4 No lastmod file - disabling lastmod-related functionality Can't open file /usr/local/aspseek/var/aspseek/ranksd: No such file or directoryRanks size: 0 Started accepting queries on port 12345 Regards Claus Jul Larsen -----Oprindelig meddelelse----- Fra: Kir Kolyshkin [mailto:[EMAIL PROTECTED]] Sendt: 19. april 2001 21:25 Til: [EMAIL PROTECTED] Emne: Re: SV: [aseek-users] Re: kill -SIGHUP searchd, re-read searchd.conf? Well we do not experience such behaviour. Anyway, please try 1.1.4 and report your results. Claus Jul Larsen & Anne Smed Nielsen �����(�): > > Hi Kir, > > Do you solve the problem with searchd ? I've now only one site on the > aspseek base. Two and more sites will destroy search and a core will be > dumped. Do you have recived the conf and more from me? > > Regards > > Claus Jul Larsen -- [EMAIL PROTECTED] http://kir.sever.net ICQ 7551596 -- Every rule has an exception, except the rule of exceptions Now listening to Scooter "I'm Your Pusher"
