On Sun, Jun 05, 2005 at 02:41:00PM -0700, Victor Babitchev wrote:
> access to sbox location (try/result): 1st/OK 2nd/500 3rd/OK 4th/500
Try starting apache in single process mode using -X option.
For example:
/usr/sbin/apache-perl -f $(pwd)/test.conf -X
Those changing results seem like they might be coming from different
apache processes.
> .. the only thing till now that I found & that helps me in this story - is
> to place 'x' in front of the hash line "date_ranges" in swish.cgi - then
> all works fine!?
That's disabling the date select feature. That's fine, if you don't
want to use that.
> Also I believe that my swish-e 2.4.0 installation is OK, it was done 1 year
> ago, all tests were OK and I had just fun & no troubles since then (Linux
> suse 8.2, 2.4.20-64GB-SMP; Apache/1.3.27 (Linux/SuSE) PHP/4.3.1
> mod_perl/1.27; SWISH-E 2.4.0;)
I just installed 2.4.0 and changed my Apache config file to point to
the new version:
<perl>
use lib '/home/moseley/2.4.0/lib/swish-e';
require "swish.cgi";
</perl>
and no problems. Don't know what else to tell you.
> <perl>
> use lib '/srv/www/cgi-bin/mediasrv'; # location of the swish.cgi file
> use lib '/usr/local/lib/swish-e/perl'; # modules required by swish.cgi
> require "swish.cgi";
> </perl>
You should not need that second line. When you installed swish-e the
swish.cgi file was created with the correct paths based on your
installation.
Notice that the script already has the correct "use lib" line to find
modules required by swish.cgi:
moseley@bumby:~$ fgrep 2.4.0 2.4.0/lib/swish-e/swish.cgi
use lib qw( /home/moseley/2.4.0/lib/swish-e/perl );
swish_binary => '/home/moseley/2.4.0/bin/swish-e', # Location of swish-e binary
INCLUDE_PATH => '/home/moseley/2.4.0/share/swish-e',
path => '/home/moseley/2.4.0/share/swish-e',
--
Bill Moseley
moseley@hank.org
Unsubscribe from or help with the swish-e list:
http://swish-e.org/Discussion/
Help with Swish-e:
http://swish-e.org/current/docs
swish-e@sunsite.berkeley.edu
Received on Sun Jun 5 19:57:33 2005