I've noticed on both my gentoo desktop and my RedHat 7.3 laptop that when I run a cronjob that uses updatedb to update the slocate database, my memory usage (not cached memory, nor buffer memory, but memory reported by the kernel as being used by programs) spikes to well over 300 MB. I'm usually in X when this happens, but quitting X does not not give me back my memory, and I can sit and watch the memory usage grow while updatedb runs. In order to get that memory back, what I have been doing is rebooting, which is a no-no in my book. I should never have to reboot for something like this. Has anyone else had this problem? Anyone have any suggestions on a fix?
Grant ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
