Bug 163340 - PRUNEFS and PRUNEPATHS appear to be environmental variables but aren't.
PRUNEFS and PRUNEPATHS appear to be environmental variables but aren't.
Product: Fedora
Classification: Fedora
Component: slocate (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Miloslav Trmač
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-07-15 07:33 EDT by Jonathan Werrett
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-15 15:48:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Werrett 2005-07-15 07:33:04 EDT
Description of problem:

In slocate's /etc/updatedb.conf PRUNEFS and PRUNEPATHS appear to be used
as environmental variables. Eg. they are exported and
/etc/cron.daily/slocate.cron source's the conf file before running updatedb.

However, updatedb ignores the environment and reads the conf file (whose
location is compiled in), looking for the lines that start with PRUNEFS and

Version-Release number of selected component (if applicable):

How reproducible:

Have a /etc/updatedb.conf like this:
PRUNEFS="sysfs selinuxfs usbdevfs devpts NFS nfs afs sfs proc smbfs cifs autofs
auto iso9660 udf"
PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /net /sfs /selinux /udev /mnt/floppy"
export PRUNEFS
PRUNEPATHS="$PRUNEPATHS /data /data1 /data2 /aerialcache"
Actual results:

/usr/bin/updatedb will have an affective PRUNEPATHS of
"/tmp /usr/tmp /var/tmp /afs /net /sfs /selinux /udev /mnt/floppy"

Expected results:

If PRUNEPATHS was being read as an environmental, you'd expect this:
"/tmp /usr/tmp /var/tmp /afs /net /sfs /selinux /udev /mnt/floppy /data /data1
/data2 /aerialcache"
Comment 1 Miloslav Trmač 2005-07-15 15:48:25 EDT
Thanks for your report.

This was fixed in FC4: there are no 'export' lines in /etc/updatedb.conf,
and updatedb.conf(5) documents the file format.
/etc/cron.daily/slocate.cron still sources the file unfortunately.

Note You need to log in before you can comment on or make changes to this bug.