pk writes: > So why does it prune files with bigger size than about 4Gb? The only > thing I can think of is that my machine is 32bit... But why would > slocate use file size as a factor?
I can confirm the problem on my 32bit machine with default updatedb.conf. I had to emerge slocate first for that, though - normally I am using mlocate, which does NOT show the problem. So using mlocate instead of slocate would be a workaround, and mlocate is supposed to be faster than slocate anyway. https://fedorahosted.org/mlocate/ Wonko
