Home › Forums › OS X Server and Client Discussion › File Serving › Mounted Volumes & mds, mdsync, mdimport
- This topic has 3 replies, 2 voices, and was last updated 18 years, 9 months ago by
Anonymous.
-
AuthorPosts
-
September 29, 2005 at 8:19 pm #363407
dragonmac
ParticipantA couple of Questions if someone could clue me in. I going to Tiger and am deeply concerned with this indexing with the problems I’ve had in the Past with Apple/indexing. (some of you may remember)
First some background OSX Server 10.3.7, Clients are OS 9 MMgr, and 10.3.7 Network Homes.
My plan was this All OS 9 Client are getting Mini’s 10.4.2 Network Homes first(Homes should just link up but we will see some early tests seem fine).
10.3.7 Client to 10.3.9 till i get my Radmind & base 10.4.2 image for them setup.
Then Server to 10.3.9 Followed by 10.4.2 ASAP. (If anyone has input on this rollout especially problems please post them even if they are off-topic)
To the Topic at hand:
1. Will mds force an index of the Mount Volume?
2. Will each new Tiger Unit index the 10.3.7-9 Server Volumes as mounted and if they don’t finish what happens?
3. What kind of Network overhead are we talking about here if indexing happens on the Client level?
4. How big are these indexes? And Mounted Volume indexes local or on Mounted?
5. Network overhead on a Mounted Volume Spot-Search?Ok you see where I’m headed with this So feel free to point out any problem you have had with this Spotlight. This had better not be another Sherlock set of problems with indexes on Servers.
September 30, 2005 at 5:11 pm #363425Anonymous
GuestAFAIK network homes can not use spotlight
July 17, 2006 at 12:07 pm #366626Anonymous
GuestHello,
I have the opposite problem: We have networked homedirs in our university lab (AFP with a Novell NetWare 6.5 server), and I *don’t* want to have Spotlight active as we must minimize our server traffic.
My problem is: After killing mds (or at user login time), the local root can’t disable Spotlight indexing to his networked homedir, I think it’s because he has no rights on our Novell server:
# mdutil -s [NETWORKED_HOMEDIR]
Error: Could not get indexing status for volume.After a while of heavy network traffic, apparently indexing has finished, and he can:
# mdutil -s [NETWORKED_HOMEDIR]
Status: Indexing Enabled# mdutil -i off [NETWORKED_HOMEDIR]
Indexing disabled for volume.I want to exclude Spotlight access at login time. Do you see any possibility of doing so? (Of course, I could disable Spotlight completely and give “EasyFind” to our users, but that renders the search bars useless, and our users are no Mac experts).
Thanks for reading,
Viktor. -
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed