Mantis - findutils
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4076 regular use tweak sometimes 2009-12-10 10:58 2011-05-14 14:59
Reporter: jh Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0004076: gupdatedb should check if it's still running
Description: I didn't check the whole script but I looks like there is no check.

Reason: When the gfind stuff takes longer then a day. ( e.g. somtimes on the buildfram because it's called by every zone) It's started again. Which could have bad effects on the system performance.
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2009-12-10 10:58 jh New Issue
2011-05-14 14:59 jay Note Added: 0009047

Notes
(0009047)
jay   
2011-05-14 14:59   
You can just mutually exclude multiple runs by using "lockfile -l 60" or similar.

If the problem is NFS performance, then you can build a locate database on the NFS server and have the clients all search that by using LOCATEPATH (as long as all the clients mount the exported filesystem in the same place). Then you just add nfs to the list of filesystems updatedb doesn't search.