Skip to main content.
home | support | download

Back to List Archive

Re: Searching with meta tags ---> can't make it

From: Bill Moseley <moseley(at)not-real.hank.org>
Date: Thu Dec 13 2001 - 13:37:17 GMT
At 10:50 PM 12/12/2001 -0800, Rick Ciaccio wrote:
>Ok, here's a lasp gasp before I abandon Swish-e...

I can't remember what you are trying to do -- index metanames or to NOT
index metanames, so here's both.  I'm using -D to dump the index, which is
not pretty in 2.0.5, but is shows exactly what's in the index.

 > cat 1.html
<META NAME="keyName" CONTENT="keynameword">
<META NAME="metaother" CONTENT="metaotherword">
foo

./swish-e -i 1.html

./swish-e -D index.swish-e -v 4

-----> WORD INFO <-----
foo: Meta:1 1.html Rank:38698 Strct:1 Freq:1 Pos:1
keynameword: Meta:1 1.html Rank:38698 Strct:1 Freq:1 Pos:1
metaotherword: Meta:1 1.html Rank:38698 Strct:1 Freq:1 Pos:1

All words indexed, as metaID 1 (the default).


swish-e-2.0.5/src > cat c
MetaNames keyName

./swish-e -c c -i 1.html
./swish-e -D index.swish-e -v 4

-----> WORD INFO <-----
foo: Meta:1 1.html Rank:38698 Strct:1 Freq:1 Pos:1
keynameword: Meta:2 1.html Rank:38698 Strct:1 Freq:1 Pos:1
metaotherword: Meta:1 1.html Rank:38698 Strct:1 Freq:1 Pos:1

Ok, so it's indexing as a metaname.  MetaID 2 is "keyname" meta.

> ./swish-e -w keyname=keynameword -v 0
# Swish-e format 2.0
# Indexed on: 13/12/2001 05:09:12 PST
# Search words: keyname = keynameword
# Number of hits: 1
1000 1.html "1.html" 97

So now you don't want "metaotherword" indexed?

#define REQMETANAME 1 in config.h
make

./swish-e -c c -i 1.html
./swish-e -D index.swish-e -v 4

-----> WORD INFO <-----
foo: Meta:1 1.html Rank:58047 Strct:1 Freq:1 Pos:1
keynameword: Meta:2 1.html Rank:58047 Strct:1 Freq:1 Pos:1

Now it's gone.


>	romanoskyphoto% ./swish-e -c site.conf
>	Indexing Data Source: "File-System"
>	swish: Couldn't open the configuration file "site.conf".

I doubt the filesystem is not telling the truth.  site.conf doesn't exists
in that directory.


>me know... I would rather not hear "upgrade", it is not an option on 54 
>servers.

If you want the features of 2.1 you need to upgrade.  It's well worth it.
You are going to have to copy the recompiled 2.0.5 to all 54 machines
anyway, so I don't follow your argument that it's not an option.  Maybe
someone here (or your system admin) can help you with a shell script to
deploy to your servers.  Might be a nice script to have around.  I've used
rdist before.  Surely the time you have spent trying to get 2.0.5 to do
something easy in 2.1 is more than the time it takes to scp to 54 machines
in a shell script.  And probably less time than it took me to download and
compile 2.0.5 and run the above examples for you.

If you need more help make sure you cut-n-paste your command exactly from
your session, and read 

 http://www.swish-e.org/2.2/docs/INSTALL.html#QUESTIONS_AND_TROUBLESHOOTING

but realize that the debugging methods described there are for 2.1 not 2.0.5.

So, I'd recommend upgrading...



Bill Moseley
mailto:moseley@hank.org
Received on Thu Dec 13 13:37:23 2001