🚀 go-pugleaf

In article <3vl6kn$is2@explorer.csc.com> sallen@csc.com (Steven Allen) writes:

	   Does anybody know why I keep getting the following error
   when cron runs updatedb?   

	   Find: /proc/self/fd/4  No such file or directory

The /proc filesystem is a neat way of accessing kernel and process information.
In particular, the /proc/self tree gives information about the current process
resources; /proc/self/fd lists file descriptors used by the process. What happens
here is 'updatedb' has descriptor 4 open when it collects the filesystem information,
and it gets closed by the time find runs. 

I suppose updatedb should bypass /proc filesystem, as it is not a real
disk-based filesystem. This can be done by modifying this line in 'updatedb'

test -z "$PRUNEREGEX" &&
  PRUNEREGEX='\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)'

to say 

test -z "$PRUNEREGEX" &&
  PRUNEREGEX='\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/proc$\)'

or perhaps /proc/self rather than /proc.
--
			przemek klosowski (przemek@rrdstrad.nist.gov)
			Reactor Division (bldg. 235), E111
			National Institute of Standards and Technology
			Gaithersburg, MD 20899,      USA

			(301) 975 6249