|Anonymous | Login||2023-12-05 07:07 CET|
|Main | My View | View Issues|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0004076||[findutils] regular use||tweak||sometimes||2009-12-10 10:58||2011-05-14 14:59|
|Summary||0004076: gupdatedb should check if it's still running|
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.
|Tags||No tags attached.|
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.
|Copyright © 2000 - 2008 Mantis Group|