Re: [cobalt-users] .Glmpse (was Qube 2 hang solution found)

[Malcolm McLeary <mmcleary@xxxxxxx>]

Hi Mike,

on 18/11/01 4:56 AM, Mike Vanecek at nospam99@xxxxxxxxxxxx wrote:

> :>Another alternative is to edit buildSearchIndex.pl to constrain what it
> :>actually indexes.  If your Qube is being used as a fileserver then I think
> :>its pretty pointless indexing all those Mac and Windows files as you can't
> :>use the web interface to access the files anyway.
> :>
> :>There is a line in buildSearchIndex.pl
> :>
> :># add directories to index below as needed (within quotes)
> :>
> :>the next line is
> :>
> :>my $gIndexDirs = '"/home/users" "/home/groups"';
> :>
> :>I recommend changing it to
> :>
> :>my $gIndexDirs = '"/home/groups/home"';
> :>
> :>I keep all web stuff in /home/groups/home so its the only bit worth indexing
> :>... doing all user and group files is a waste of resources.
> 
> Any reason you took that approach as opposed to editing the
> .glimpse_include and .glimpse_exclude files?

I felt that what I did restricted the scanning and traversing directories.
It was my understanding thattThe include and exclude files would only get
invoked after it scanned to determine whether the info was to be included in
the index.  

I wanted to restrict the scanning process not just what was in the index.

Cheers,  Malcolm

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

                       Information Alchemy Pty Ltd
                             ACN 089 239 305
                           Canberra, Australia

Malcolm McLeary                                Mobile:     0412 636 086
Managing Director                              Email:  mmcleary@xxxxxxx

     This message was sent using Outlook Express 5.0 for Macintosh.