Description of problem: On one (Athlon) machine I see recently pretty consistently these: /etc/cron.daily/slocate.cron: line 3: 9934 Segmentation fault /usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e "/tmp,/var/tmp,/usr/tmp,/afs,/net" mailed by cron. I _think_ that this really coincides with a recent update to kernel-2.4.18-27.7.x. In /etc/cron.daily/slocate.cron I commented out "renice +19 -p $$ >/dev/null 2>&1" line and this appears to help. At least I did not a message like above from the last night where they were otherwise a fixture. Version-Release number of selected component (if applicable): slocate-2.6-1 How reproducible: I do not observe that on other machines which are somewhat related both hardware-wise and software-wise. A different memory layout?
Today I received a similar mail from my cron daemon. /etc/cron.daily/slocate.cron: /etc/cron.daily/slocate.cron: line 3: 7209 Segmentation fault /usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e "/tmp,/var/tmp,/usr/tmp,/afs,/net" /usr/bin/run-parts: line 36: 7275 Segmentation fault $i 2>&1 7276 | awk -v "progname=$i" 'progname { print progname ":\n" progname=""; } { print; }' /usr/bin/run-parts: line 36: 7444 Done $i 2>&1 7445 Segmentation fault | awk -v "progname=$i" 'progname { print progname ":\n" progname=""; } { print; }' It's slocate-2.6-8 on a RH9 system with kernel 2.4.20-20.9.
Please verify this with a newer version of Red Hat Enterprise Linux or Fedora Core and reopen it against the new version if it still occurs. Closing as "not a bug" for now.