Bug 57897
Summary: | slocate no longer works with glibc-2.2.4 | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Ville Herva <v> |
Component: | slocate | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-24 22:23:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ville Herva
2001-12-31 06:45:34 UTC
I just rechecked with my backup - using these: rpm -q glibc glibc-2.2.3-19.1 rpm -q slocate slocate-2.4-1 it works. Ummh, it ain't that. Witness: 2001-12-16: >chroot /backup-versioned/2001-12- 16T052001 /bin/zsh >mv /var/lib/slocate/slocate.db /var/lib/slocate/slocate.db.back >/etc/cron.daily/slocate.cron <exits imediately> >L /var/lib/slocate/slocate.db* -rw-r----- 1 root slocate 1 Dec 31 08:54 /var/lib/slocate/slocate.db -rw-r----- 1 root slocate 1 Dec 16 04:50 /var/lib/slocate/slocate.db.back >mv /var/lib/slocate/slocate.db.back /var/lib/slocate/slocate.db >rpm -q glibc slocate glibc-2.2.4-18 slocate-2.4- 1 >rpm -V glibc slocate S.5....T /etc/cron.daily/slocate.cron >md5sum =slocate /etc/updatedb.conf /etc/cron.daily/slocate.cron /lib/i686/libc.so.6 /lib/libnss_files.so.2 efd7af5b68421e8379f2830b9b8d1abe /usr/bin/slocate 2132d4bc1fa63e44cd92fb0ae40cdc8d /etc/updatedb.conf 10d1ab4b969754774f28352d25a7ef19 /etc/cron.daily/slocate.cron 83119f8da8abfc2a05c036bdfb8d2eeb /lib/i686/libc.so.6 4a7f9e44cfcdf8572523e613bcb07c0e /lib/libnss_files.so.2 2001-12-14: >chroot /backup-versioned/2001-12-14T052001 /bin/zsh >mv /var/lib/slocate/slocate.db /var/lib/slocate/slocate.db.back >/etc/cron.daily/slocate.cron <ctrl-c> >ls -l /var/lib/slocate/slocate.db* -rw-r----- 1 root slocate 4845689 Dec 14 04:57 /var/lib/slocate/slocate.db.back -rw-r----- 1 root slocate 249856 Dec 31 08:58 /var/lib/slocate/slocate.db.tmp root@babbage:/>rpm -q glibc slocate glibc-2.2.4- 18 slocate-2.4-1 root@babbage:/>rpm -V glibc slocate S.5....T /etc/cron.daily/slocate.cron root@babbage:/>md5sum =slocate /etc/updatedb.conf /etc/cron.daily/slocate.cron /lib/i686/libc.so.6 /lib/libnss_files.so.2 efd7af5b68421e8379f2830b9b8d1abe /usr/bin/slocate 2132d4bc1fa63e44cd92fb0ae40cdc8d /etc/updatedb.conf 10d1ab4b969754774f28352d25a7ef19 /etc/cron.daily/slocate.cron 83119f8da8abfc2a05c036bdfb8d2eeb /lib/i686/libc.so.6 4a7f9e44cfcdf8572523e613bcb07c0e /lib/libnss_files.so.2 So something extraordinary broke between 14th and 16th, but what on Earth could it be? I may have upgraded something, but I don't recall, what. >cat /etc/updatedb.conf PRUNEFS="devpts NFS nfs afs proc smbfs autofs auto iso9660" PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /net" export PRUNEFS export PRUNEPATHS >cat /etc/cron.daily/slocate.cron #!/bin/sh /usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e "/tmp,/var/tmp,/usr/tmp,/afs,/net,/backup- versioned,/home/sftp/jail" Ok, I found out the crucial difference. I had changed rootfs type from ext3 to auto in /etc/fstab.(updatedb read mtab, not fstab, but the auto setting propagates to there frm fstab.) If I change /dev/hdf3 / auto rw 0 0 to /dev/hdf3 / ext3 rw 0 0 in mtab, and rerun updatedb, it works. And look and behold, "auto" is excluded by default in /etc/updatedb.conf I'm not sure what is the default in fstab for redhat-7.2 or rawhide, "auto" or "ext3"? Propably "ext3"? ext3. We haven't used auto for local filesystems. So you have a (good) reason to exclude fs type auto in updatedb.conf? Perhaps you could add this to FAQ or something? I think it was pretty nasty problem to solve from end user point of view. Thanks. |