Tony Bibbs wrote:
>
> Can you explain more on the "fixed ranks reloading" from below?
The first four bytes of ranks file is its version. Before each
query processing searchd checks if version has changed (index
changed it), and if new_ver!=old_ver it reload ranks file again.
We used fread in versions prior to 1.0.4. It have some strange
effect (caching?) - it read old data instead of new, so ranks
file wasn't reloaded. In 1.0.4 we use read, which have no such
problem.
> Is that
> what keep my siteweights from working properly?
I think no. Please describe your situation in details.
>
> Kir Kolyshkin wrote:
> >
> > Hi,
> >
> > We have just released ASPSeek v.1.0.4. Changes are:
> >
> > Fixed bug with robots.txt
> > Fixed processing links with apostrophes
> > Small fixes to INSTALL, searchd.conf, s.htm, Makefiles
> > Searchd binds to loopback if access is allowed only from localhost
> > Fixed HTTP basic authorization support
> > Added s.cgi ability to accept several ul= arguments
> > Fixed processing tags with symbol '>' inside
> > Fixed potential buffer overflows in s.cgi
> > Fixed escaping some SQL queries
> > Fixed ranks reloading
> > Fixed rare searchd coredump when sorting results by date
> > s.cgi now prints charset in Content-Type header (not in META)
> > In case of SQL query error bad query is printed
> >
> > This version fixes some security holes in s.cgi, so it would
> > be very wise decision to upgrade immediately.
> >
> > Enjoy,
> > Kir.
> >
> > -- [EMAIL PROTECTED] http://kir.sever.net ICQ 7551596 --
> > Answers: $1, short: $5, correct: $25, dumb questions are still free.
-- [EMAIL PROTECTED] http://kir.sever.net ICQ 7551596 --
Answers: $1, short: $5, correct: $25, dumb questions are still free.
