James, Thanks a million for your question and comment. see my response inline. If there is anything unclear or wrong, please feel free to let me know
Jim > Shi-Ying Irene Huang writes: > >> SUNWslocate Uncommitted package name >> /usr/bin/slocate Volatile CLI >> /usr/bin/updatedb Volatile CLI >> > > 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. /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. > 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. > ... 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. >> /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.
