Irene: The description for this project says:
> This locate can index all files on your system, but only files > and directories which the invoking user has access to will be > displayed. This doesn't really explain to me what exactly this project does very well. I don't, for example, understand how it is different (or how it relates) to other projects that do similar things - such as MetaTracker. Will having multiple services on the system which are indexing all the files on a system have performance impact? This isn't discussed at all. Brian Irene Huang wrote: > Hi, all > > The new proposal files is uploaded to > Internally > http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal-v2.txt > Diff: http://sac.eng/Archives/CaseLog/arc/LSARC/2008/447/proposal.diff > > Externally > http://www.opensolaris.org/os/community/arc/caselog/2008/447 > > if there's any further issues with this case, please send an email > before 07/22/2008. > > Thanks in advance. > > --Irene > On Mon, 2008-07-21 at 18:18 +0800, Jim Li wrote: >> Hi James, >> >> I've updated the one page and summarized the questions and answers. >> >> Q1. Missed at least /etc/updatedb.conf and /var/lib/slocate/slocate.db >> >> added the missed interfaces. see the updated one page. >> >> Q2. Missed a contract. What is being used from /usr/lib/libast.so.1 and why? >> >> The contract has been approved. >> >> http://sac.sfbay/Archives/CaseLog/arc/LSARC/2008/447/contracts/libast-PSARC-2006-550.txt >> >> Fts_open, fts_close, fts_read and fts_set provide the functionality >> of traversing a file hierarchy. They are GNU C library extension but >> not in Solaris's libc. >> >> Q3. What's this software integrating? >> >> Java Desktop. >> >> Q4. Suggested that each locate implementation has an update service in >> smf(5) >> and a cron job. >> >> Currently we are focusing on enriching the open source projects which can >> be used on Solaris. Don't have enough resources to improve the projects or >> provide extension function. >> >> In Linux distribution, slocate use anacron to update the index file >> periodically. Anacron is a little bit different from cron job. It >> executes commands at intervals not at specifed time. It does not >> assume that the system is running continuously. >> >> If this is a blocked issue of this case, please feel free to let me know as >> soon as possible. I'll discuss this issue with my manager. >> >> Q5. Does user need special privileges to execute updatedb? >> >> needs Primary Administrator profile. >> >> Q6. There's locate(1) versus slocate(1) versus mlocate(1). Aren't Linux >> distributions dropping slocate over time? >> >> mlocate is a locate/updatedb implementation. The 'm' stands for "merging". >> updatedb reuses the existing database to avoid rereading most of the file >> system, which makes updatedb faster and does not trash the system caches >> as much. mlocate could be a replacement for locate but not slocate. >> >> slocate skips the files and directory which the invoking user hasn't right >> access without stoping the locate. mlocate only focuses on creating index >> files effectively. >> >> In Ubuntu 7.10, locate has been overwritten by slocate if slocate has >> been installed. >> >> I do hope that the review can be restarted. >> >> Thanks >> Jim >>> Jim Li writes: >>> >>>>> Shi-Ying Irene Huang writes: >>>>> I think you may have missed at least /etc/updatedb.conf and >>>>> /var/lib/slocate/slocate.db. There may be other interfaces associated >>>>> with this package; I'm not positive, as it's been a while since I used >>>>> it. >>>>> >>>>> >>>>> >>>> /etc/updatedb.conf is the configuration file for locate which belongs to >>>> another package findutils. As slocate man pages says that slocate will >>>> parse GNU Locate's /etc/updatedb.conf when the argument is provided. >>>> >>> OK. That still makes it an interface. Interface lists aren't just a >>> catalog of the files shipped in the package. >>> >>> >>>> /var/lib/slocate/slocate.db is the index file which is be created by >>>> package install post, cause it's group owner should be slocate which is >>>> created by package install pre. I'm not sure if I should list this file >>>> here or not. If it should be there, please let me know. >>>> >>> Yes; absolutely. The "install post" and "install pre" sound like an >>> interesting problem as well. The new user and group are *also* >>> interfaces. >>> >>> You should work with your case sponsor to come up with a complete set >>> of materials. I suggest placing this case in "waiting need spec" >>> state until those materials are available, because it's obviously not >>> complete today, and thus can't be a fast-track. >>> >>> >>>>> Isn't updatedb normally used only in a cron job entry? Should it be >>>>> on every user's path, especially with that really unfortunate, >>>>> much-too-generic name? >>>>> >>>>> >>>>> >>>> Not really. Sometime user need to update index immediately. >>>> >>> I see. Does that user need special privileges to do this? >>> >>> >>>>> ... and then there's locate(1) versus slocate(1) versus mlocate(1). >>>>> Aren't Linux distributions dropping slocate over time? >>>>> >>>>> >>>>> >>>> In Ubntu 7.10, locate has been overwritten by slocate if slocate is >>>> installed. >>>> >>> What about mlocate? >>> >>> >>>>>> /usr/lib/libast.so.1 private 2006/550 >>>>>> (SONMAE libast.so.1) >>>>>> >>>>>> >>>>> That comes from ON and I don't see a contract. Where's this software >>>>> integrating? >>>>> >>>>> >>>>> >>>> Contract is going on, Sorry about this. Libast.so.1 is in SUNWcsl. >>>> >>> Where is slocate integrating? SFW? >>> >>> > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc at opensolaris.org
