Unable to use 'locate' to locate files mlocate.db permission denied
Bug #281471 reported by
Alin Claudiu Radut
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mlocate (Debian) |
Fix Released
|
Unknown
|
|||
mlocate (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I'm using Hardy on a 1000h. When I'm trying to locate a file using locate I receive
$ locate gdm
locate: can not open `/var/lib/
I listed /var/lib/locate and mlocate.db seems to be owned by root and group mlocate
$ ls -al /var/lib/mlocate
total 3204
drwxr-xr-x 2 root root 4096 2008-10-11 00:33 .
drwxr-xr-x 51 root root 4096 2008-10-06 21:01 ..
-rw-r----- 1 root mlocate 3266135 2008-10-11 00:33 mlocate.db
Changed in mlocate (Ubuntu): | |
status: | New → Confirmed |
Changed in mlocate (Debian): | |
status: | Unknown → Incomplete |
Changed in mlocate (Debian): | |
status: | Incomplete → Fix Released |
To post a comment you must log in.
Probably the same issue as for crontab: /bugs.launchpad .net/ubuntu- eee/+bug/ 269265 /answers. launchpad. net/ubuntu- eee/+question/ 46970
https:/
... and for ping, reported here:
https:/
So presumably the real question is why these don't have the same suid/sgid setting as in a vanilla ubuntu hardy install... I doubt it is an intentional change?