Thanks! Did you see my second mail? I just want to tell that after
correcting the name to the swish-index-db in swish.cgi and my .swish.conf
the problem disappeared. I thought that when using .swish.conf would
override the conf-settings in swish.cgi when using mod_perl. For some reason
it did not for the swish-index. But, it worked and i think better than
loading-perl-and so on for the requests. However, I will try to get the
'search.cgi' using SWISH::API to work as you suggests....when I tried that
(sortly) there were problems between Template-toolkit (the *.tt file) and
'search.cgi' .....the search.fields did not show??? but in a day or two I
will try again. Thanks again.
----- Original Message -----
From: "Bill Moseley" <email@example.com>
To: "Peter Morling" <firstname.lastname@example.org>
Cc: "Multiple recipients of list" <email@example.com>
Sent: Monday, May 03, 2004 8:31 PM
Subject: Re: Running swish-e on windows with mod_perl and apache - fork
> On Mon, May 03, 2004 at 02:49:50AM -0700, Peter Morling wrote:
> > ---
> > -e open2: Can't close: at C:/Apache2/search/search.cgi line 2173
> > Failed to flush STDOUT: Invalid argument.
> Would you be able to try and write a very small mod_perl program that
> just calls IPC::Open2::open2() to run an external program? Then try a
> few programs (other than swish) to see how common it is.
> Again, I don't think that's the best way to use swish from mod_perl
> (SWISH::API is the way to go), but you may have come across a bug in
> mod_perl that should be reported.
> Info on reporting mod_perl bugs can be found at:
> Bill Moseley
Received on Mon May 3 12:11:56 2004