Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Possible problems?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Possible problems?
Authored by: dzurn on May 04, '05 01:18:49PM
I don't have Tiger yet, but from the Ars Technica discussion of Spotlight, the index for a file is automatically updated when the Tiger Kernel is used to save the file. That means that potentially other user's modifications to a network share would not be updated automatically (and it's not clear if your own modifications would, if the saving is done other than by the kernel).

And it appears each user would have to reindex the shared volume for themselves. Keep in mind that you can't query Spotlight while it's updating an index, so I don't think you could use Spotlight on your local drive while the network drive indexes were being updated.

Intriguing, but I'd love to see more exploration of this topic for sure!

---
Madness takes its toll.
Please have exact change.

[ Reply to This | # ]

Re: Possible problems?
Authored by: ldm on May 04, '05 03:36:41PM

You are correct on all counts. If a share is modified by another machine/user the change would not be visible. This is not meant to serve that purpose though. In this case, I have a 'personal' file server that holds quite a bit of data and I am the sole person accessing it (it is my home directory on the server). I still have problems if I access the share in read/write from two distinct machines. I guess that to resolve this one the only option is to use Tiger Server (and throw away the linux box in the process to get a Mac...) . I am told that with Tiger Server, the indexing happens on the server... which of course solves the issue since the client forwards its queries to the server and all is well.



---
--
Laurent



[ Reply to This | # ]