On Thu, Jul 28, 2005 at 04:28:52AM +0200, Miloslav Trmac wrote: > The package is prepared to install alongside slocate (it actually requires > slocate because I didn't want to allocate a GID for mlocate yet): > configure it at /etc/mupdatedb.conf and then just use (mlocate) instead > of (locate). Couldn't mlocate just reuse (or use in parallel) the same gid? Both entities should have the same security implications, so separating the user/group ownership wouldn't help much. BTW another feature often asked for in *locate is the ability to merge different databases (usually from different nfs filesystems from different hosts) into a super locatedb. Would that extension be easy in mlocate (which already has merging code inside)? -- Axel.Thimm at ATrpms.net
Attachment:
pgpLVy7lPDeNi.pgp
Description: PGP signature