Re: updatedb fails on F7....

From: "Doncho N. Gunchev" <gunchev@xxxxxxxxx>
Date: Sun, 30 Sep 2007 22:14:28 +0300

On Sunday 2007-09-30 21:40:38 Globe Trotter wrote:

so what is the solution to this, as root?

# updatedb
updatedb: src/updatedb.c:721: scan_cwd: Assertion `name_size > 1' failed.
Aborted

How much time does it take it to give this message? Generally speaking you
should call /etc/cron.daily/mlocate.cron, which will tell updatedb what
not to index (ex: /dev, /proc, /sys, /selinux, /tmp...). Maybe one of
these pseudo filesystems is causing the problem, try mlocate.cron?

--
Regards,
Doncho N. Gunchev, GPG key ID: 0EF40B9E, Key server: pgp.mit.edu

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Follow-Ups:
- Re: updatedb fails on F7....
  - From: Globe Trotter

References:
- updatedb fails on F7....
  - From: Globe Trotter

Prev by Date: Re: Error: kernel cannot suspend to ram.
Next by Date: Re: Error: kernel cannot suspend to ram.
Previous by thread: updatedb fails on F7....
Next by thread: Re: updatedb fails on F7....
Index(es):
- Date
- Thread

Relevant Pages

Re: updatedb fails on F7....
... Generally speaking you ... which will tell updatedb what ... these
pseudo filesystems is causing the problem, ... Updatedb commad aborts unless /sys
directory is pruned ... (Fedora)
Re: updatedb fails on F7....
... Doncho N. Gunchev wrote: ... Generally speaking you ... which
will tell updatedb what ... Registered Linux User #374218 ... (Fedora)