From: jjg on
hello, *

I am running Slack 12.1, and I try to do an updatedb, which never seems to
finish. Last time I had a similar problem, one of my file systems was
corrupted. However, when I checked this morning, all file systems were
clean.
Suggestion, anyone?
From: Henrik Carlqvist on
jjg <jjge(a)xs4all.nl> wrote:
> I am running Slack 12.1, and I try to do an updatedb, which never seems to
> finish.

You could try "strace -p" on the pid of updatedb to see what it is doing.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Michael Black on
On Sun, 29 Jun 2008, jjg wrote:

> hello, *
>
> I am running Slack 12.1, and I try to do an updatedb, which never seems to
> finish. Last time I had a similar problem, one of my file systems was
> corrupted. However, when I checked this morning, all file systems were
> clean.
> Suggestion, anyone?
>
The first time after the install, it sure seems to take time. Of course,
later it usually runs as a cron job late at night so you don't notice.

Did you have any DVDs or CDs mounted at the time? I seem to recall
doing that at least once, and it would add to the time since it's
territory that hasn't been databased yet.

Michael

From: Giovanni on
On 06/29/08 20:04, jjg wrote:
> hello, *
>
> I am running Slack 12.1, and I try to do an updatedb, which never
> seems to finish. Last time I had a similar problem, one of my file
> systems was corrupted. However, when I checked this morning, all
> file systems were clean. Suggestion, anyone?

Do you have an NFS mounted? If the remote machine is not responding
updatedb lasts forever.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
Registered Linux user #337974 < http://giovanni.homelinux.net/ >
From: Helmut Hullen on
Hallo, jjg,

Du meintest am 29.06.08:

> I am running Slack 12.1, and I try to do an updatedb, which never
> seems to finish. Last time I had a similar problem, one of my file
> systems was corrupted. However, when I checked this morning, all file
> systems were clean.
> Suggestion, anyone?

Maybe you use the original "/etc/updatedb.conf" which uses wrong
delimiters for "PRUNEPATH" ans "FSPATH".

"man slocate" and "man updatedb" show that "slocate" needs "," as
delimiter, not " ".

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".