| It would probably be easier if you just ran these same
commands from a terminal/console so that all messages come back to your
screen.
Looking at the database 'last modification date' may give
an indication of whether anything is happening, and at the same time have a look
at the size of all files. If at all possible, get hold of an old set of
databases from a backup to show you how big they should be, as everyone's will
be different.
Would also be worth checking what happens when you run a
search from the command line?
Regards,
Mike
Ok thanks. I
don't think it's running at all because there are lots of pages on this
server, I'm almost certain that it's not running at all because hte page
doesn't even take 1 second to show the results (literally). The search
function did index something however because it does show some old results but
nothing new. What would you suggest if the index isn't working at
all?
I think you need to put back in a little of the
script that you originally showed us, or else point that part to a physical
file, from what little (rusty) PERL I can remember, the script currently
isn't configured to print to screen. Even without the vees, you should
be getting some output from the -s option, once the dig has
completed. It may also be worthwhile checking the actual process usage on
that machine, to ensure that the task has actually completed. I presume your
document base must be fairly small; normal running times are measured in
minutes and hours, not seconds.
Mike
Hi, nothing at
all prints to the screen when I perform that. ; Here is a copy of the
file that I'm using.
print "Content-type:
text/htmlnn";
if($ENV{'QUERY_STRING'} eq
'do'){
print
"<HTML><BODY><PRE>--HTDIG
Results--n";
print `./bin/htdig
-s`;
; print "nn";
print
"--HTMERGE Results--n";
print `./bin/htmerge
-s`;
; print
"</PRE></BODY></HTML>";
}else{
print
qq~<html>
<body>
<;p><a
href="htdigindexer.cgi?do">Do
Index</a></p>
</body>
<;/html>
~;
}
|
bellsouth.