CrunchBang Linux

satex

New Member

Registered: 2012-10-01

Posts: 3

[SOLVED] Locate/updatedb Issues

Hello,

After I first installed #! the other day, I thought I has used locate and updatedb but for some reason it is not letting me anymore. I then figured out that I didn't have locate installed so I went ahead and installed it from synaptic which installed updatedb of course with it. I tried using it after I installed it but it was not returning any results so I rebooted my machine. BTW, I am running sudo updatedb. After the machine came back up I ran sudo updatedb but it kept telling me that permission was denied. However, the location of updatedb was not where I thought it should be but maybe I am wrong. Here is the output I get when running sudo updatedb:

user@crunchbang:~$ sudo updatedb
[sudo] password for user: 
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied
/usr/bin/find: `/home/user/.gvfs': Permission denied

I feel like it should not be in the 'find' directory but I am not sure. Any assistance would be much appreciated! Thanks!

satex

Last edited by satex (2012-10-06 23:24:33)

Digit

#! Die Hard

From: the internet

Registered: 2009-05-26

Posts: 972

Website

Re: [SOLVED] Locate/updatedb Issues

idk.

maybe adding/removing locations from updatedb.conf might remove these error messages.

does locate still work though?  do new files get picked up by updatedb so locate can find them, i mean...

if so, then maybe these error messages dont hurt anything more than terminal scroll/screen space.

(hehe, that felt weird, doing a "locate updatedb.conf", just to check that was what updatedb's config is called)

Last edited by Digit (2012-10-06 16:39:09)

---

in honour of Aaron H. Swartz,
make liberating JSTOR (and similar)'s database(s) of knowledge from behind paywalls your #1 priority,
and keep making the world a better place.
live up to what he lived for.

xaos52

The Good Doctor

From: Planet of the @s

Registered: 2011-06-24

Posts: 4,267

Re: [SOLVED] Locate/updatedb Issues

I recall getting that message once when running updatedb. Well, I got the message every time I ran updatedb, but it displayed only once.
Locate worked as expected.
Running it now on a Debian sid system, there is no error message at all.

Last edited by xaos52 (2012-10-06 17:00:58)

---

bootinfoscript - emacs primer - I ♥ #!

satex

New Member

Registered: 2012-10-01

Posts: 3

Re: [SOLVED] Locate/updatedb Issues

Thanks Digit and xaos52. I just sat down to take a look at this again and ended up finding an article relating to .gvfs corrupting directories. I was able to remove it by:

#umount /home/useraccount/.gvfs
#find . -inum 554009 -exec rm{} \;

After that,

#rm -rf .gvfs

I didn't even rm/install locate, it just worked after that. Thanks for your help!

satex