Messages in this thread | | | Date | Thu, 05 Feb 2004 20:45:15 -0800 | From | "Martin J. Bligh" <> | Subject | Re: Limit hash table size |
| |
>> > But I've been telling poeple for a year that they should set >> > /proc/sys/vm/swappiness to zero during the updatedb run and afaik nobody has >> > bothered to try it... >> >> I do not think such hacks are the right way to do. If updatedb does not >> do that backup will or maybe your nightly tripwire run or some other >> random application that walks file systems. Hacking all of them is just not >> realistic. > > You need some way of not slowing down real-world applications by a factor > of 1000. That is unacceptable, and the problems which updatedb and friends > cause (just once per day!) pale in comparison.
I still think this needs to be on a per-process basis, rather than system wide - it's updatedb that's the problem here, not the time of day. Personally, I'd just trigger on processes that were niced to hell, but I'm sure other people have other ways.
M.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |