"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? --
