Title: AW: AW: [aseek-users] small problems (v1.2.8): index and s.cgi

good hint with ScriptLog ....

but the script displays nothing:

%% [Tue Jan 15 12:53:54 2002] GET /cgi-bin/swnav.cgi.127?q=hilfe&cs=iso-8859-1 H
TTP/1.0
%% 500 /httpd/wnav/cgi-bin/swnav.cgi.127
%request
Accept: application/msword, application/vnd.ms-excel, application/vnd.ms-powerpo
int, image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Accept-Encoding: gzip, deflate
Accept-Language: de
Cache-Control: max-age=259200
Host: wuppertal-navigator.de
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0; QXW0333v)
Via: 1.1 A011-34:8080 (Squid/2.4.STABLE1), 1.0 www-cache.interproxy:8083 (Squid/
2.4.STABLE1), 1.0 www-cache.dmzproxy.firewall:8080 (Squid/2.4.STABLE1)
X-Forwarded-For: 130.11.64.41, unknown, 193.109.238.138
%response



Markus Rietzler
* kommunikation & online service
* RZF NRW
* Tel: 0211.4572-130



-----Urspr�ngliche Nachricht-----
Von: Kir Kolyshkin [mailto:[EMAIL PROTECTED]]
Gesendet am: Dienstag, 15. Januar 2002 10:41
An: [EMAIL PROTECTED]
Betreff: Re: AW: [aseek-users] small problems (v1.2.8): index and s.cgi

"Markus Rietzler " wrote:

>         s.htm is readable and executable by group www, this should be enough.
>         this also works with the s.cgi of aspseek 1.2.5. they both use the same
> s.htm
>         but even if s.htm is not readable shouldn't s.cgi complain about it - maybe
> on STDERR -
>         when i call it via command prompt?
>
>         is it ok, that s.cgi is only about 30k? think the hole stuff is in the lib,
> right?

yes

>
>         do i have to put the libaspseek.so in a special dir? is it enough if it is
> found in
>         /opt/aspseek/lib?
>         btw: i have setup aspseek with a symlink. while compling i uses
> prefix=/opt/aspseek.127
>         (ok, this is not really perfect at the moment...)
>
>         lrwxrwxrwx   1 root     root           11 Jan 12 15:16 aspseek ->
> aspseek.127
>         drwxr-xr-x   8 rit      users        4096 Jun 22  2001 aspseek.125
>         drwxr-xr-x  10 rit      www          4096 Jan 12 15:14 aspseek.127

s.cgi "knows" where its lib is.

Try to set up apache cgi debugging so you will see s.cgi's output
See http://httpd.apache.org/docs/mod/mod_cgi.html#scriptlog for details

--
[EMAIL PROTECTED]  ICQ 7551596  Phone +7 903 6722750
Hard work may not kill you,  but why take chances?
--

Reply via email to