On 2006-10-15 Guy Coates <[EMAIL PROTECTED]> wrote:
> Andreas Metzler wrote:
>> On 2006-10-15 Guy Coates <[EMAIL PROTECTED]> wrote:
>>> Package: findutils
>>> Version: 4.1.20-6
>>> Severity: normal

>>> updatedb / find is trying to index filesystems even though both the
>>> filesystem type and paths are set in PRUNEFS and PRUNEPATHS and
>>> should be ignored.

>>> /etc/updatedb.conf has the following lines,

>>> PRUNEFS="NFS nfs nfs4 afs proc smbfs autofs iso9660 ncpfs coda devpts ftpfs 
>>> devfs mfs sysfs shfs sysfs cifs lustre_lite gpfs"
>>> export PRUNEFS
>>> PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /amd /alex /var/spool /sfs /GPFS 
>>> /data/blastdb /GPFS/data1 /GPFS/tmp1 /lustre"
>>> export PRUNEPATHS

>>> However, updatedb still indexes the following 3 filesyetems of type
>>> lustre_lite and mounted under /lustre.
>> [...]

>> Are you running updatedb manually or does this happen when run from
>> the cron-job (which sources /etc/updatedb.conf)?


> This is from the cron job.


I have not got lustre running here, but I fail to be able to reproduce
the bug:

argenau:~# mkdir -p /lustre/scratch /lustre/blastdb
argenau:~# touch /lustre/xxx /lustre/blastdb/yy /lustre/scratch/zzz
argenau:~# /etc/cron.daily/find ; locate lustre
/lustre
/lustre/blastdb
[...]

If I am adding /lustre to /etc/updatedb.conf /lustre lustre is not
indexed anymore.
argenau:~# /etc/cron.daily/find ; locate lustre
argenau:~# 

There is no general bug with stuff that is excluded _both_ by PRUNEFS
and PRUNEPATHS. If I move /lustre to /dev/shm/ (tmpfs) which is
already included in PRUNEFS *and* add /dev/shm/lustre to PRUNEPATHS it
also is not included.
argenau:~# /etc/cron.daily/find ; locate lustre
argenau:~# 

cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to