|
Bugzilla – Full Text Bug Listing |
| Summary: | findutils-locate is not able to locate anything | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jason Kasper <vR> |
| Component: | Basesystem | Assignee: | Andreas Schwab <schwab> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jason Kasper
2005-08-24 17:13:10 UTC
Don't remove /media from UPDATEDB_PRUNEPATHS. I don't know how to do what you're talking about, so I doubt that I have done it. How would I check to see what this configuration setting is? Okay, I just checked in /etc/sysconfig/locate has this: UPDATEDB_PRUNEPATHS="/mnt /cdrom /tmp /usr/tmp /var/tmp /var/spool /proc /media" I haven't changed it. I haven't "removed /media from UPDATEDB_PRUNEPATHS." I'm re-opening this as your solution doesn't fix the problem. Help, please? Also, I don't understand why /media/floppy is getting auto-mounted when I boot. I have commented out /media/floppy from /etc/fstab, and still I get this when I run `mount`: /dev/fd0 on /media/floppy type subfs (rw,nosuid,nodev,sync,fs=floppyfss,procuid) I do not have a floppy disk in /dev/fd0, so I think that it's a bug that /media/ floppy gets mounted at boot. That may be aggravating/causing the bug that I've reported here. Thanks for your help! =:) You didn't pass the right options to updatedb. Here's the thing... You can keep closing this as INVALID, but I really don't
think it is. Have you actually taken the time to try this?
I have installed beta1 as a clean/full install. I have installed the
appropriate package via yast and have not tampered with it, nor have I changed
any settings whatsoever. I have upgraded via yast to the latest beta. And if I
let the cron job do updatedb (with whatever settings are default), what I see
the next day is that if I run something extremely simple, such as "locate
passwd", I get no results and a return code of 1.
Now, I just ran "strace -f locate passwd", what I see is this (at the bottom):
stat64("/var/lib/locatedb", {st_mode=S_IFREG|0644, st_size=62, ...}) = 0
open("/var/lib/locatedb", O_RDONLY|O_LARGEFILE) = 3
time([1125497053]) = 1125497053
fstat64(3, {st_mode=S_IFREG|0644, st_size=62, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40027000
read(3, "\0LOCATE02\0\0Your password has exp"..., 4096) = 62
read(3, "", 4096) = 0
close(3) = 0
munmap(0x40027000, 4096) = 0
close(1) = 0
exit_group(1)
And, what I see if I do a "cat /var/lib/locatedb" is this:
LOCATE02Your password has expired. Choose a new password.
Does that sound to you like this is an invalid bug? I don't think so. It does
look to me that there is another problem here. Can you please help me with it?
Thanks very much.
*** This bug has been marked as a duplicate of 103873 *** Thank you Andreas! =:) |