From: "Rich"
This is a multi-part message in MIME format.
------=_NextPart_000_00F0_01C621D6.15E4C530
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
WDS and Index Server can ignore one anothers indexes. Even if they =
didn't, the files aren't of a support type so would only have metadata =
(name, size, etc) indexed.
Rich
"Gregg N" wrote in message =
news:43d80524{at}w3.nls.net...
Rich,
Thanks.
One of the two computers did have the thunderbird beta filter =
(protocol handler) installed. I uninstalled it, and rebuilt the index. I =
will see if it stops doing the unnecessary reindexes now.
The other computer did not have any additional filters installed. =
However, I did notice that it also had the indexing service enabled, =
which I now disabled. Does WDS and Indexing Service each know not to =
index the other's index file?
Installing WDS did not turn off the indexing service.
The only message in the application or system event log from WDS was a =
system event indicating installation of hotfix KB907371-V2.
Gregg
"Rich" wrote in message news:43d6fc19$1{at}w3.nls.net...
If the index is corrupted it gets rebuilt. Did you install any =
third party IFilter implementations? Buggy ones may crash causing =
problems. I know some would crash though its been a while since one =
triggered a rebuild of my index.
I'd also look in the event log. I think an event gets logged =
when corruption is detected. My memory is fuzzy on this.
Rich
"Gregg N" wrote in message =
news:43d683ad{at}w3.nls.net...
Every so often (maybe a couple of times a day) Windows Desktop =
Search=20
decides that it needs to do a massive reindexing of 20,000 or so =
files. The=20
status dialog shows that it is scanning seemingly unrelated =
directories that=20
I have not touched in ages (e.g., "c:\Program Files\Microsoft =
Platform=20
SDK\", "c:\cygwin", etc.).
Once it is finished, it stays at "items left to scan: 0" for a few =
hours=20
until it decides to do it again.
Anyone know what triggers this? It does this on two different =
computers,=20
both XP Pro.
While it is at 0, it behaves normally. If I create a new file, it =
briefly=20
jumps up to 1 and then after 15 seconds of computer idle, it goes =
back to 0=20
again, as I expect.
WDS version: 02.06.0000.2083
Gregg
------=_NextPart_000_00F0_01C621D6.15E4C530
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
WDS and
Index Server can =
ignore one=20
anothers indexes. Even if they didn't, the files aren't of a =
support type=20
so would only have metadata (name, size, etc) indexed.
Rich
"Gregg N" <invalid{at}invalid.invalid>">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid>
= wrote in=20
message news:43d80524{at}w3.nls.net...
Rich,
Thanks.
One of the two computers did have the thunderbird =
beta=20
filter (protocol handler) installed. I uninstalled it, and rebuilt the =
index.=20
I will see if it stops doing the unnecessary reindexes =
now.
The other computer did not have any additional =
filters=20
installed. However, I did notice that it also had the indexing service =
enabled, which I now disabled. Does WDS and Indexing Service each =
know=20
not to index the other's index file?
Installing WDS did not turn off the indexing=20
service.
The only message in
the application or system =
event log=20
from WDS was a system event indicating installation of hotfix=20
KB907371-V2.
Gregg
"Rich" <{at}> wrote in message news:43d6fc19$1{at}w3.nls.net...
If
the index is =
corrupted it gets=20
rebuilt. Did you install any third party IFilter=20
implementations? Buggy ones may crash causing problems. =
I know=20
some would crash though its been a while since one triggered a =
rebuild of my=20
index.
I'd
also look in the =
event=20
log. I think an event gets logged when corruption is =
detected. =20
My memory is fuzzy on this.
Rich
"Gregg N" <invalid{at}invalid.invalid>=20">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid>=20
wrote in message news:43d683ad{at}w3.nls.net...Ev=
ery=20
so often (maybe a couple of times a day) Windows Desktop Search=20
decides that it needs to do a massive reindexing of 20,000 or =
so=20
files. The status dialog shows that it is scanning seemingly =
unrelated=20
directories that I have not touched in ages (e.g., "c:\Program =
Files\Microsoft Platform SDK\", "c:\cygwin", =
etc.).Once it is=20
finished, it stays at "items left to scan: 0" for a few hours =
until it=20
decides to do it again.Anyone know what triggers this? It =
does=20
this on two different computers, both XP
Pro.While it =
is at 0,=20
it behaves normally. If I create a new file, it briefly jumps =
up to 1=20
and then after 15 seconds of computer idle, it goes back to 0 =
again,=20
as I expect.WDS version:=20
=
02.06.0000.2083Gregg=
BODY>
------=_NextPart_000_00F0_01C621D6.15E4C530--
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
SEEN-BY: 633/267 270 5030/786
@PATH: 379/45 1 106/2000 633/267
|