ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

News and Reviews > Mini-Reviews by Members

Locate 3.0 - great *FAST* HD search tool!

<< < (21/33) > >>

f0dder:
:huh: it took two days here? Typically I'm not so slow.

f0dder: ahh ok, I though that you meant user's own folder
-jmj (January 06, 2008, 08:37 AM)
--- End quote ---
Nope, just meant per-user folders&shares on the server, still keeping locate indexing and the database files on the server. But I can see that my post wasn't very clear :)

vixay:
vixay, Howabout if you create one database for IT, another for HR and third for OP and keep database files in server?
-jmj (January 06, 2008, 04:57 AM)
--- End quote ---
That's what I was trying to say :)
-f0dder (January 06, 2008, 06:26 AM)
--- End quote ---

suggestion by jmj: vixay, Howabout if you create one database for IT, another for HR and third for OP and keep database files in server?


The problem with that is like this:
*Server*
IT.dbs stored in C:\Dept\IT (shared as \\Server\IT) and indexes only C:\Dept\IT (so file links are local!)
HR.dbs stored in C:\Dept\HR (shared as \\Server\HR) and indexes only C:\Dept\HR (so file links are local!)
OP.dbs stored in C:\Dept\OP (shared as \\Server\OP) and indexes only C:\Dept\OP (so file links are local!)
Locate32.exe stored in C:\Apps (shared as \\Server\Apps)

*User*
IT User: maps \\Server\IT to X:\ or can connect via UNC \\Server\IT
HR User: maps \\Server\HR to X:\ or can connect via UNC \\Server\HR
OP User: maps \\Server\OP to X:\ or can connect via UNC \\Server\OP
Management User: maps \\Server\Dept to Y:\
    therefore Y:\IT = C:\Dept\IT ...etc. for all depts

All users map \\Server\Apps to V:\
They can import settings for all databases, but won't have access to other departments databases. The can run Locate via V:\Apps\Locate32\Locate32.exe

*Updates*
Are done on the server for each database via scheduling.

*Searching*
Is done by users on their PCs

When they search they need references to resolve either
a) to their local drives (X:\filefound.txt) or
b) to UNC paths (\\Server\HR\filefound.txt)

but now, it resolves to C:\Dept\HR\filefound.txt!
and doesn't work for them!

The paths are different for each user!
for example:
on server:    C:\Dept\HR\filefound.txt
on HR user:   X:\filefound.txt or \\server\hr\filefound.txt
on Mgmt User: Y:\HR\filefound.txt


_current pains_
importing settings into each users pc

_possible solutions_

have 1 master user from each type who updates database, while the rest only search.
This would resolve the path issue from each users perspective, but it would be inefficient as you'd be indexing the same content 2-3 times! Plus you'd need special priveleges for that particular user to be able to update the database


any other ideas? I hear there are corporate search solutions or intranet scripts but those are slow compared to locate32 find as you type results.

_features in locate32 that would make this easier_

- portability (i.e. settings don't need to be imported)
- show results based on how files are accessible to user. i.e. Locate can put a KEYFILE at the root of each path it is indexing. Then locate the KEYFILE from the users current PC, and prepend the path to all the entries in a databse while displaying results. or allow user to add custom prefix/suffix to results.

then the deployment would be easier i think, for each database.


Or maybe i am crazy to think like this. Any better ideas?

vixay:
http://www.locate32.net/forum/viewtopic.php?f=9&t=82

link to locate32 forum where i posted this request.

Carol Haynes:
I have been experimenting with Locate for network use (just by adding folders on some NAS I have and folders on other PCs on the network).

I find everything runs fine when they are all switched on but as soon as some of the paths are not available Locate takes ages to load - worse even if I remove the network paths from the index or even rebuild my DB from scratch using only local discs Locate still waits ages when you try and load it.

The only way I could get back to instant response was to use YourUninstaller to remove all traces of Locate and then reinstall from scratch.

f0dder:
I find everything runs fine when they are all switched on but as soon as some of the paths are not available Locate takes ages to load - worse even if I remove the network paths from the index or even rebuild my DB from scratch using only local discs Locate still waits ages when you try and load it.
-Carol Haynes (January 11, 2008, 05:41 AM)
--- End quote ---
Yeah, I'm bitten by this thing as well, since I spin down the harddrives on my fileserver - when using locate, they spin up. It should be possible to run locate in a "don't check if the files still exist, only return results" mode...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version