https://bugzilla.novell.com/show_bug.cgi?id=259579 Summary: With expanding disk space and competition to provide fast file finding utilities it is perhaps necessary to integrate Linux "locate" into the options of File Find or kfind Product: openSUSE 10.2 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@tpg.com.au QAContact: qa@suse.de With disk space expanding all the time more than ever it is required to have a tool to locate files and provide filter options is a smaller space of time. Linux locate command has only been used in the GUI application Krusader to my knowledge. I think it is timely and necessary to compete with opposition M$ to offer index based searching. To this end I think we need a new process to run in every system that will execute 'updatedb' I do not think that running updatedb as a cron job once a day is sufficient. Rather than run as a service to execute updatedb a several instances in time I think its execution needs to have a few more smarts and execute under the following and a "Fast Find option be added as an option from the Kfind application, however it is not to be included in the kfind application. This would facilitate the application being removed without harming Kfind, enable a user to exclusively execute "Fast Find" from the desktop, if proven by time to be of great value, be offered as a separate menu item from Kfind. 0. There are to be 2 different values of ALL variable parameters hereunder. The presence of any of the following services should indicate the use of second value. In ALL circumstances updatedb should be run from the Root directory of ANY Volume either logical or physical. The existence of either a shared directory OR NFS drive should be executed by the owner of the shared drive and the IP of the NFS server respectively. ALL devices consider to be of a CD/DVD in nature are always exempt from this service despite being mounted at time time. A. The presence of an NFS Server service B. The presence of an HTTP/FTP service C The presence of an Mail Transfer Client. 1 System resources are less than x AND updatedb has not been run for X minutes. 2. Updatedb should be executed at ANY startup of any system AND updatedb has not been run for X minutes. 3. If system resources are above X and below Y AND updatedb has not been run for X minutes then updatedb will be executed on the Z time execution of updatedb. 4. If execution is delayed by any of above then a W time frame for execution is created. 5. If system resources are above Y AND updatedb has not been run for X minutes AND W delays have been recorded then a warning is issues at start of Kfind requesting execution by the user 6. If W == X or is too close in V minutes to execution then W is ignored and X is maintained 7. During the execution of updatedb IF system resources exceed U then 4 as above is to be applied. 8. updatedb NOW should be an option in kfind with perhaps the following expression. 1. Update Disk indexing NOW to permit fast find. 9. ALL parameters above with the exception of W are dynamic in value and are subject to the instances of W. 10 The W parameter is self dynamic in value All execution or non execution of updatedb is to be logged and reason supplied. It is anticipated that the above may be extended to Finding Applications, not be application current name, this would be foolish, but be application type I.E Word, Word Processor, Document, Document creator, Calculator, Create CD, DVD, Internet, Browser -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.