At 12:22 22.04.2002, you wrote: >Did you create different s.htm from s-128.cgi and s-125.cgi ? > >Alexander.
Yes, I did. There is aspseek/etc/s.htm (for 125) and aspseek128/etc/s-128.htm to satisfy the need for a corresponding s.htm file in the program directory. When compiling Aspseek 1.2.8, the path to the program directory is burned into to binaries, /usr/local/aspseek128 in my case. A 128 binary like s-128.cgi should therefore reference templates in /usr/local/aspseek128/etc only, and the searchd from 128 should use the config file searchd.conf from there, too. The searchd.conf file in the 128 directory clearly points to db.conf and uses port 12348, see excerpts from these files below: db.conf: DBAddr mysql://<user>:<pw>@localhost/aspseek128/ searchd.conf: Include db.conf #Port 12345 Port 12348 AllowFrom 127.0.0.1 DataDir /data/aspseek128 ... Question: Did anybody succeed in running two concurrent versions of Aspseek on the same box? Regards Frank #-------------------------------------------------------# Dipl.-Math. Frank Elsner Universitaet Osnabrueck (University of Osnabrueck) - Rechenzentrum - (Computing Center) Albrechstrasse 28, AVZ D-49076 Osnabrueck Deutschland (Germany) Tel. (Phone): ++49 (0)541/969-2343 Fax: -2470 E-Mail: [EMAIL PROTECTED] #-------------------------------------------------------#
