On Mon, 2003-03-31 at 11:29, Grant Robinson wrote: > 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?
That memory should be freed once updatedb is done running. Is it not? I've never had updatedb take so much memory. But then, I haven't been killing it regularly either. If you never reboot, you might just want to change the cron job to run at 2 AM. Then when you notice your memory spiking it'll be a reminder to go to bed. -- Stuart Jansen <[EMAIL PROTECTED]> #define FALSE 0 /* This is the naked Truth */ #define TRUE 1 /* and this is the Light */ -- mailto.c
signature.asc
Description: This is a digitally signed message part
