[bug #4391] Race condition in find causes spurious error messages in updatedb

[nobody]

=================== BUG #4391: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4391&group_id=61

Submitted by: ametzler                Project: findutils                    
Submitted on: Mon 07/21/2003 at 11:22
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Originator Name:                      
Originator Email:                     Status:  Open                         
Release:  None                        Fixed Release:  None                  

Summary:  Race condition in find causes spurious error messages in updatedb

Original Submission:  Generate a big tree:
mkdir `seq -w 000 999` 
for i in a b c d e ; do find -type d -exec touch '{}'/$i ; ; done

Run find and rm at the same time:
{ for i in * ;do rm -rf  $i ; done ; } & LANG=C find ./ -type f -print > 
/dev/null
[1] 390
find: ./004/c: No such file or directory
find: ./004/d: No such file or directory
find: ./004/e: No such file or directory
find: ./005: No such file or directory
[...]

Usually it does not matter, but it requires one to run updatedb with >/dev/null 
2>&1, losing the real errors. Otherwise you'll get a silly mail from cron every 
other day, when it fails to stat some lockfile (fetchmail.lck), some spoolfile 
from lpd or a moved mail in a mailfolder.

http://bugs.debian.org/67782

          cu andreas



No Followups Have Been Posted


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4391&group_id=61

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/