Carlos E. R. wrote:
And something still remains broken in my system which I have not yet "located".
Notice that mlocate is different from locate:
Telcontar:~ # l /var/lib/mlocate/mlocate.db - -rw-r--r-- 1 root root 54014689 Oct 25 22:20 /var/lib/mlocate/mlocate.db Telcontar:~ #
It is owned by root. And it works:
Telcontar:~ # su - nobody nobody@Telcontar:~> locate mlocate.db /usr/share/man/man5/mlocate.db.5.gz /var/lib/mlocate/mlocate.db /var/lib/mlocate/mlocate.db.VXAzte nobody@Telcontar:~> logout Telcontar:~ #
--- How can you say it works AND that something is broken on your system because it doesn't do the access checks? I.e. you are claiming it is both working and broken: It should only be readable by group locate (or mlocate--whatever), or root. Your installation has access control disabled because mlocate.db is world readable. mlocate is *open source*, which means that if the "db" is readable by all, you can use your own, non-access checking version of mlocate to find files that you shouldn't be able to. Only if the database is protected will mlocate enforce access control. I.e. mlocate-access checking is broken because the instructions are *right*, FOR the access-controlled version of mlocate. Your system is configured to disable those checks by having mlocate.db being world readable.
"You do not need to belong to that group, the instructions are plain wrong:" __[sic]__ "rpm -qi mlocate User must be member of locate group in order to use this package."
If you don't want to do access checks, then you don't need to be a member of group locate and the mlocate.db needs to be world readable. If you want to do access checks, then you need mlocate SGID([m]locate) and the .db only readable by group [m]locate). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org