htdig-dev Mailing List for ht://Dig (Page 93)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

On Wed, 6 Mar 2002, Debra C. Clark wrote:

> Will the htdig work on an apache server?

Of course.

--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/

Will the htdig work on an apache server?

Debra C. Clark
Quantum Research Intl.

I'm trying to figure out why one of my directories is getting skipped.

The start_url list has:
http://careermatters.tvo.org
http://careermatters.tvo.org/highschool/show_groups.phtml 
http://careermatters.tvo.org/afterhs/apprenticeship/college.phtml

The links on the third URL are in one of two formats:
- /afterhs/apprenticeship/index.phtml
- schools.phtml?inst_id=28&level_id=college

I have no problems crawling the second type of URL in a different directory 
(2nd URL). Any ideas of why it might not be working here? In fact none of 
the words on 3rd start URL are indexed either.

(Unfortunately the site is password protected at this point, please email 
me off-list for the u:p.)

Thanks!

emma

Hi,

I have installed htdig succesfully on redhat 6.2.
I have a directory with around 1000 .xml files which i need to create a database for a search using htdig.These xml files are all resumes.
Ive tried all possibilities but when i get the page for the htdig search i dont get the resumes which i enter for a search,but i get the default search pages e.g if i type apache , and then click search i do get few urls etc ie i get default search urls.
Please do respond explaining on how to create a search database so that i can do a rundig and get all related files i need.Ive been stuck with this for around a month.

Awaiting a favourable response,

Regards,

Melwin Fernandes.
Sr. Executive-Technical Infrastructure
Princeton Software Exports
Mumbai-India.

>Willy Calderon's bits of Tue, 5 Mar 2002 translated to:
>
> >-I../htlib -I../htcommon  -I../db/dist -I../include -g Accents.cc
> >        CC -o htfuzzy -L../htlib -L../htcommon -L../db/dist -L/usr/lib
> >Endings.o EndingsDB.o Exact.o  Fuzzy.o Metaphone.o Soundex.o  
>SuffixEntry.o
> >Synonym.o htfuzzy.o  Substring.o Prefix.o Accents.o 
>../htcommon/libcommon.a
> >.../htlib/libht.a  ../db/dist/libdb.a -lz -lnsl -lsocket
> >ld32: FATAL   12 : Expecting n32 objects: /usr/lib/crt1.o is o32.
> >*** Error code 2 (bu21)
> >*** Error code 1 (bu21)
> >
> >================
> >
> >
> >Any ideas?
>
>If I recall correctly, there are a couple 32-bit addressing
>schemes used under IRIX. The older is referred to as o32 and the
>newer as n32. It appears that your objects are being built as n32
>(by default), but an attempt is being made to link with an o32
>system object.
>
>You either need to build htdig using -o32 or link against an n32
>version of crt1.o. Do you have another copy of crt1.o somewhere?
>Perhaps in /usr/lib32? If so, you should be able to check if it
>is n32 with the 'file' command. If you can find the n32 version,
>I believe you can set an LDFLAGS environment variable before
>running configure in order to make the build process look in the
>alternate location. For example
>
>  > setenv LDFLAGS -L/usr/lib32
>  > ./configure
>
>The other option would be to leave LDFLAGS as is and pass
>everything a -o32.
>
>Sorry if this is a bit vague in places. My IRIX experience is
>quite limited.
>
>Jim

OK, I setenv LDFLAGS L/usr/lib32 and the ./configure and it ran.  Again, 
during the make process, I get another error except this time previous 
warnings in /usr/lib32/

=====================

        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g htfuzzy.cc
        CC -o htfuzzy -L/usr/lib32 -L../htlib -L../htcommon -L../db/dist 
-L/usr/lib Endings.o EndingsDB.o Exact.o  Fuzzy.o Metaphone.o Soundex.o  
SuffixEntry.o Synonym.o htfuzzy.o  Substring.o Prefix.o Accents.o 
../htcommon/libcommon.a  ../htlib/libht.a  ../db/dist/libdb.a -lz -lnsl 
-lsocket
ld32: WARNING 84 : /usr/lib32/libz.so is not used for resolving any symbol.
ld32: WARNING 84 : /usr/lib32/libnsl.so is not used for resolving any 
symbol.
ld32: WARNING 84 : /usr/lib32/libsocket.so is not used for resolving any 
symbol.
ld32: ERROR   33 : Unresolved text symbol "alloca" -- 1st referenced by 
../htlib/libht.a(regex.o).
        Use linker option -v to see when and which objects, archives and 
dsos are loaded.
ld32: INFO    152: Output file removed because of error.
*** Error code 2 (bu21)
*** Error code 1 (bu21)

=====================

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

Hi,

Can someone please tell me what type of indexer htdig is? Is it =
statistical, probabilistic, boolean etc? This makes a big difference for =
the current application I'm trying to develop and I still haven't found =
an indexer!!

Thanks in advance,

Melissa

Hi all:

I'm indexing a four section site. Three of the sections are indexing fine, 
but the fourth is not. I've tried adding new URLs to the conf file, but it 
doesn't seem to help. It's a PHP site and the file extensions are .phtml. 
Also, the first page of each section has a swf file with all the links in 
it, so I've had to feed htdig.conf URLs for pages that are below the index 
page.

Unfortunately this site is under development and is currently password 
protected. Please email me off list if you have some ideas and I can give 
you the info to get in to the site. (I don't want the username/password 
showing up in list archives...)

Thanks a bunch!!

emma

Willy Calderon's bits of Tue, 5 Mar 2002 translated to:

>-I../htlib -I../htcommon  -I../db/dist -I../include -g Accents.cc
>        CC -o htfuzzy -L../htlib -L../htcommon -L../db/dist -L/usr/lib
>Endings.o EndingsDB.o Exact.o  Fuzzy.o Metaphone.o Soundex.o  SuffixEntry.o
>Synonym.o htfuzzy.o  Substring.o Prefix.o Accents.o ../htcommon/libcommon.a
>.../htlib/libht.a  ../db/dist/libdb.a -lz -lnsl -lsocket
>ld32: FATAL   12 : Expecting n32 objects: /usr/lib/crt1.o is o32.
>*** Error code 2 (bu21)
>*** Error code 1 (bu21)
>
>================
>
>
>Any ideas?

If I recall correctly, there are a couple 32-bit addressing
schemes used under IRIX. The older is referred to as o32 and the
newer as n32. It appears that your objects are being built as n32
(by default), but an attempt is being made to link with an o32
system object.

You either need to build htdig using -o32 or link against an n32
version of crt1.o. Do you have another copy of crt1.o somewhere?
Perhaps in /usr/lib32? If so, you should be able to check if it
is n32 with the 'file' command. If you can find the n32 version,
I believe you can set an LDFLAGS environment variable before
running configure in order to make the build process look in the
alternate location. For example

 > setenv LDFLAGS -L/usr/lib32
 > ./configure

The other option would be to leave LDFLAGS as is and pass
everything a -o32.

Sorry if this is a bit vague in places. My IRIX experience is
quite limited.

Jim

Thanks for the info.  Turns out the license.dat details weren't updated yet 
for the C++ compiler.  D'oh!!

In any case, I've done a
./configure
make

but it stalls in the make process with the following error:

================
a - defaults.o
        : libcommon.a
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Endings.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g EndingsDB.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Exact.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Fuzzy.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Metaphone.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Soundex.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g SuffixEntry.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Synonym.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g htfuzzy.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Substring.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Prefix.cc
        CC -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" 
-I../htlib -I../htcommon  -I../db/dist -I../include -g Accents.cc
        CC -o htfuzzy -L../htlib -L../htcommon -L../db/dist -L/usr/lib 
Endings.o EndingsDB.o Exact.o  Fuzzy.o Metaphone.o Soundex.o  SuffixEntry.o 
Synonym.o htfuzzy.o  Substring.o Prefix.o Accents.o ../htcommon/libcommon.a  
../htlib/libht.a  ../db/dist/libdb.a -lz -lnsl -lsocket
ld32: FATAL   12 : Expecting n32 objects: /usr/lib/crt1.o is o32.
*** Error code 2 (bu21)
*** Error code 1 (bu21)

================

Any ideas?

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

On Thu, 28 Feb 2002, Gilles Detillieux wrote:

> According to Bill Carlson:
> > I ran across a logical problem when handling <META name="robots" 
> > content="noindex"> on a page. The behavior expected is that links on the 
> > page will be followed and indexed. This works fine on the initial index.

> I believe this would be a problem with all 3.1.x and 3.2.0x releases.
> The problem is that when a document is marked as "noindex", it gets
> removed from db.docdb by htmerge or htpurge, so subsequent update runs
> of htdig don't check this file for changes (either in it's noindex
> status, or in the links it can harvest from it) - it's off htdig's radar
> entirely at that point.

Yes, further examination showed this is the exact problem. It is a small 
problem, once known, with two work arounds that I see: do an initial dig 
every reindex or make sure any given page has a link path to it from the 
start_url that does not include noindex documents. I found that 
ht://check is very handy for the latter option. :)

Thanks,

Bill Carlson
-- 
Systems Programmer    wca...@vh...         | Anything is possible,
Virtual Hospital      http://www.vh.org/      | given time and money.
University of Iowa Hospitals and Clinics      |       
Opinions are mine, not my employer's.         | 

Greets all,

I have been working with htDig for almost a year now, and see a dramatic =
difference in the performance between version 3.1.x and 3.2.x. I am =
currently forced to use 3.2.x, because phrase searching is a necessity =
for the projects that I work on, however, the performance handicaps of =
3.2.x (indexing times and htmerge instability) make using it very time =
consuming for large-scale indexes (over 50,000 documents).  How =
difficult or how far away is the addition of phrase searching to the =
stable release? That is the key feature for several people I have talked =
to that would be the biggest improvement in the stable release. I've =
worked somewhat-extensively with other information retrieval systems - =
would it be easier to use the phrase search code of another public =
system as a template for implementing phrase capability?

I would love to contribute to the development effort if I could get some =
specific direction on what would need changing in htDig to enable =
phrases.

Ravi Starzl
ViWire

Richard Kraus's bits of Fri, 1 Mar 2002 translated to:

>I am over my head trying to figure htdig software out...but need to.  Is
>there anyone I can send my header/footer/wrapper etc. files to?  Someone w=
ho
>could explain whey I=B9m having this problem:

Generally anything you need to send should be sent to the list.
That usually gives you the best chance for a speedy response.
Also, this type of question should probably go to the general
list rather than the developer list. More eyes will see it that
way.

If you have header, footer, *and* wrapper files, that might be
your problem. I believe it is an either/or thing. The
documentation says that the wrapper replaces the header and
footer files. My understanding is that you either use the wrapper
file with $(HTSEARCH_RESULTS) separating the header and footer
portions, or you use header and footer files.

Jim

Willy Calderon's bits of Thu, 28 Feb 2002 translated to:

>checking for ostream.h... no
>checking for iostream.h... no
>checking for fstream.h... no
>configure: error: To compile ht://Dig, you will need a C++ library. Try
>installing libstdc++.
>=================
>
>This C++ library appears not to exist at present although under SGI IRIX
>6.5.3 shows that the libraries are already there.  Do I really need
>libstdc++ ?  or is your website accurate when it states that you need only
>the SGI C++ compiler?

The error is due to a failure to find an fstream.h header file.
It either doesn't exist on the system or it is not visible to
the configure script (i.e. it is in a non-standard location
or hidden by strange file permissions).

Do you know whether the file does in fact exist? And if so where
it is located? If it is not there, is there an fstream header
file (no .h extension)?

If you are working with an SGI compiler, I don't see that adding
libstdc++ will do you any good.

Jim

G=B9day......

I am over my head trying to figure htdig software out...but need to.  Is
there anyone I can send my header/footer/wrapper etc. files to?  Someone wh=
o
could explain whey I=B9m having this problem:

I getting desperate.

Thanks for your time.

Rick 

According to Bill Carlson:
> I ran across a logical problem when handling <META name="robots" 
> content="noindex"> on a page. The behavior expected is that links on the 
> page will be followed and indexed. This works fine on the initial index.
> 
> Let's call the page that shouldn't be indexed TOC (Tables Of Contents, a
> typical application)  and pages linked to the TOC are the content.
> 
> If the only link to a page of the content is on the TOC, later indexing 
> will not index that page as the bridging TOC is dropped from the list of 
> documents (this assumes any pages linking to the TOC have not been 
> modified since the last run and hence are not re-fetched). This causes the 
> page to drop from the database, it will only be picked up on the next 
> full index and dropped again on the next partial index.
> 
> I didn't see that this issue had been discussed before, would this still 
> be an issue for 3.2x?

I believe this would be a problem with all 3.1.x and 3.2.0x releases.
The problem is that when a document is marked as "noindex", it gets
removed from db.docdb by htmerge or htpurge, so subsequent update runs
of htdig don't check this file for changes (either in it's noindex
status, or in the links it can harvest from it) - it's off htdig's radar
entirely at that point.

I'd consider this a bug, but it's not one with an easy fix.  Rather than
purging the document completely when tagged as noindex, htmerge/htpurge
should purge all words associated with it, as it does now, as well as
purging any link descriptions for in in db.docdb, but it should keep
the record of this document in db.docdb (possibly flagged somehow) so it
doesn't get forgotten.  I haven't worked out the potential ramifications
of this, as far as possibilities of these records rising from the
grave and showing up as false entries in search results or some such.
I think to some extent 3.2 already deals with these "zombie" records in
htsearch, in case htpurge hasn't run yet, so it shouldn't be too hard
to fix this there.

-- 
Gilles R. Detillieux              E-mail: <gr...@sc...>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba  Phone:  (204)789-3766
Winnipeg, MB  R3E 3J7  (Canada)   Fax:    (204)789-3930

According to Geoff Hutchison:
> On Tuesday, February 26, 2002, at 08:02  PM, Neal Richter wrote:
> > 	Geoff sent me a first pass at a new version of searching based on
> > qtest.cc... anyone else do anything along those lines?
> 
> No, and right now I'm getting thumb-screws applied at work, so I haven't 
> had much free time to finish that. <fingers crossed>

Things are awfully busy at my end too.  I've just decided to take a bit
of time to tackle a few htdig bug reports and quick/easy questions this
afternoon during a momentary lull, if only to reduce the size of my inbox.

> > 'system(mv...)' calls in a couple files?  What's the consensus there?  
> > I'd
> > be happy to submit a patch to the necessary files.  It's well tested 
> > code
> > and works on windows as well.
> 
> I think the "replacement" copy code looked OK, but obviously we'll see 
> how it goes. If there's anything we've discovered along the way, it's 
> that ht://Dig seems to uncover flaws in supposedly well-tested code. ;-)

Yeah, it does seem to do that, doesn't it.  Still, copying files is
pretty straightforward stuff, as long as you deal properly with binary
files on non-UNIX systems.  Ideally, though, what htfuzzy should do is
attempt to move the file first, using rename or link/unlink, and if that
fails because it's cross-device, then copy.  That way, we're not wasting
time copying when we don't have to.  For portability, though, that means
dealing properly with systems that don't have rename(), i.e. older UNIX
systems, and systems that don't have link(), i.e. non-UNIX systems.
Whatever we work out, we should package into an htlib/movefile.c library
module loadable from anywhere in htdig, because right now at least two
separate htfuzzy modules need this, and there may be others now or in the
future.  It would be better not to have to duplicate this code everywhere.

-- 
Gilles R. Detillieux              E-mail: <gr...@sc...>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba  Phone:  (204)789-3766
Winnipeg, MB  R3E 3J7  (Canada)   Fax:    (204)789-3930

After installing a C++ compiler, I am still getting the error when 
attempting to configure the software after typing ./configure, this is what 
I get:

=================
computername # ./configure
loading cache ./config.cache
checking for a BSD compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
configuring ht://Dig version 3.1.6
checking for gcc... no
checking for cc... cc
checking whether the C compiler (cc ) works... yes
checking whether the C compiler (cc ) is a cross-compiler... no
checking whether we are using GNU C... no
checking whether cc accepts -g... yes
checking for c++... no
checking for g++... no
checking for gcc... no
checking for CC... CC
checking whether the C++ compiler (CC ) works... yes
checking whether the C++ compiler (CC ) is a cross-compiler... no
checking whether we are using GNU C++... no
checking whether CC accepts -g... no
checking for ranlib... :
checking for ar... /usr/bin/ar
checking for sh... /bin/sh
checking for sed... /sbin/sed
checking for sort... /usr/bin/sort
checking for find... /sbin/find
checking for gunzip... /usr/sbin/gunzip
checking for tar... tar
checking for acroread... /usr/bin/acroread
checking for sendmail... /usr/lib/sendmail
checking how to run the C preprocessor... cc -E
checking for AIX... no
checking for socket in -lsocket... yes
checking for t_accept in -lnsl... yes
checking for deflate in -lz... yes
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking how to run the C++ preprocessor... /lib/cpp
checking for fcntl.h... yes
checking for limits.h... yes
checking for malloc.h... yes
checking for sys/file.h... yes
checking for sys/ioctl.h... yes
checking for sys/time.h... yes
checking for unistd.h... yes
checking for getopt.h... yes
checking for strings.h... yes
checking for zlib.h... yes
checking for alloca.h... yes
checking for sys/select.h... yes
checking for wait.h... yes
checking for sys/wait.h... yes
checking for malloc.h... (cached) yes
checking for ostream.h... no
checking for iostream.h... no
checking for fstream.h... no
configure: error: To compile ht://Dig, you will need a C++ library. Try 
installing libstdc++.
=================

This C++ library appears not to exist at present although under SGI IRIX 
6.5.3 shows that the libraries are already there.  Do I really need 
libstdc++ ?  or is your website accurate when it states that you need only 
the SGI C++ compiler?

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

On Wed, 27 Feb 2002, Budd, Sinclair wrote:

> Would it be possible to produce a google like  "advanced" search page which
> has a panel to enter the  phrase  to be searched for, rather that requiring
> the user to  quote the phrase. I cannot think of how to encode the quotes

There will definitely be a "phrase" method (like the "and" and
"or" methods now). This won't really happen until I can find some time to
finish the htsearch rewrite.

--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/

re htdig 3.2.0b4
Would it be possible to produce a google like  "advanced" search page which
has a panel to enter the  phrase  to be searched for, rather that requiring
the user to  quote the phrase. I cannot think of how to encode the quotes
automatically in the search form.

Thanks
Sinclair Budd
s....@ic...

Hi everyone,

I have an issue with htdig that hopefully should be fairly
simple to resolve, however, I have managed to get $500 out
of my company to offer as a bounty to whoever manages to sort it
out.  It's a bug with date parsing on FreeBSD that means all
dates are incorrectly stored.

Please email me for more details.

Cheers,

John Senior.

--
js...@in...

Time to try to include the SSL patch permanently in, say, 3.1.7?

"Joe R. Jah" wrote:
> 
> FYI,
> 
> ssl.9                           33
> timet_enddate.1                 22
> Makefile.0                      21
> NUL.0                           16
> metadate.0                      16
> documentation.1                 16
> documentation.2                 12
> redirect.0                      10
> AdjustableLoggingPatch.tar.gz    6
> 
> Regards,
> 
> Joe

--J

At 13.33 25/02/2002 -0800, Jessica Biola wrote:
>Does anyone here compile with static linking rather
>than dynamic?  I was curious to know if there were any
>advantages or disadvantages.  Right now I'm using one
>of the snapshots.

I use dynamic, personally, but because it is my choice.

Guys, please correct me: the advantage of using shared library should come 
out when you use the code in it, at the same time (for instance you have 
more than 1 htdig running, htmerge, org htfuzzy, ... or htsearch). The 
executables are generally smaller, and the operating system when loading 
them into memory, loads the shared code it needs as well: so if you run 
multiple instances of the same program, you actually loads only the 'base' 
part of it.

This should generally slow down the execution (but I guess it is not that 
bad). On the other hand, if you choose static linking, every program is a 
standalone executable file. This might be faster, but I can't tell you the 
difference as far as performances are concerned.

Hey, guys, any comments?

Ciao
-Gabriele
--
Gabriele Bartolini - Web Programmer
Current Location: Prato, Tuscany, Italy
an...@ti... | http://www.prato.linux.it/~gbartolini | ICQ#129221447
 > find bin/laden -name osama -exec rm {} \;
-
Important:
--------------
I've experienced problems when receiving e-mail sent to the
address: an...@us.... I think I lost much of it.
So if you sent me a message, and I never replied to you,
that's probably the reason. Please update your address book to
this one: an...@ti.... Sorry and thank you!

FYI,

ssl.9                           33
timet_enddate.1                 22
Makefile.0                      21
NUL.0                           16
metadate.0                      16
documentation.1                 16
documentation.2                 12
redirect.0                      10
AdjustableLoggingPatch.tar.gz    6

Regards,

Joe
-- 
     _/   _/_/_/       _/              ____________    __o
     _/   _/   _/      _/         ______________     _-\<,_
 _/  _/   _/_/_/   _/  _/                     ......(_)/ (_)
  _/_/ oe _/   _/.  _/_/ ah        jj...@cl...

On Tuesday, February 26, 2002, at 08:02  PM, Neal Richter wrote:

> 	Geoff sent me a first pass at a new version of searching based on
> qtest.cc... anyone else do anything along those lines?

No, and right now I'm getting thumb-screws applied at work, so I haven't 
had much free time to finish that. <fingers crossed>

> 'system(mv...)' calls in a couple files?  What's the consensus there?  
> I'd
> be happy to submit a patch to the necessary files.  It's well tested 
> code
> and works on windows as well.

I think the "replacement" copy code looked OK, but obviously we'll see 
how it goes. If there's anything we've discovered along the way, it's 
that ht://Dig seems to uncover flaws in supposedly well-tested code. ;-)

-Geoff

Hey,
	Geoff sent me a first pass at a new version of searching based on
qtest.cc... anyone else do anything along those lines?

	I submitted a file_copy code a while back to eliminate the
'system(mv...)' calls in a couple files?  What's the consensus there?  I'd
be happy to submit a patch to the necessary files.  It's well tested code
and works on windows as well.

	Thanks!

-- 
Neal Richter 
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site

2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (47)	Nov (74)	Dec (66)
2002	Jan (95)	Feb (102)	Mar (83)	Apr (64)	May (55)	Jun (39)	Jul (23)	Aug (77)	Sep (88)	Oct (84)	Nov (66)	Dec (46)
2003	Jan (56)	Feb (129)	Mar (37)	Apr (63)	May (59)	Jun (104)	Jul (48)	Aug (37)	Sep (49)	Oct (157)	Nov (119)	Dec (54)
2004	Jan (51)	Feb (66)	Mar (39)	Apr (113)	May (34)	Jun (136)	Jul (67)	Aug (20)	Sep (7)	Oct (10)	Nov (14)	Dec (3)
2005	Jan (40)	Feb (21)	Mar (26)	Apr (13)	May (6)	Jun (4)	Jul (23)	Aug (3)	Sep (1)	Oct (13)	Nov (1)	Dec (6)
2006	Jan (2)	Feb (4)	Mar (4)	Apr (1)	May (11)	Jun (1)	Jul (4)	Aug (4)	Sep	Oct (4)	Nov	Dec (1)
2007	Jan (2)	Feb (8)	Mar (1)	Apr (1)	May (1)	Jun	Jul (2)	Aug	Sep (1)	Oct	Nov	Dec
2008	Jan (1)	Feb	Mar (1)	Apr (2)	May	Jun	Jul (1)	Aug	Sep (1)	Oct	Nov	Dec
2009	Jan	Feb	Mar (2)	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2010	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)
2011	Jan	Feb	Mar (1)	Apr	May (1)	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec
2012	Jan	Feb	Mar	Apr	May	Jun	Jul (1)	Aug	Sep	Oct	Nov	Dec
2013	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2016	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2017	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec

htdig-dev Mailing List for ht://Dig (Page 93)

htdig-dev — Developer Discussion for the ht://Dig project