On Friday 26 December 2003 16:57, Matthew Kennedy wrote: > [EMAIL PROTECTED] writes: > > when i run 'slocate' as a cron job or via CLI, > > it raises net memory usage from c 60 MB to c 200 MB & leaves it there > > (ie 'used +/- buffers/cache' in 'free'). exiting X makes no difference, > > but rebooting (naturally) restores the memory figure to the previous > > level. i've checked the forum (search 'slocate') w/o finding any mention. > > i am using the most updo-date version of 'slocate', ie 2.7-r2 . > > i have 512 MB DDR400 memory & an Athlon XP 2500+ processor. > > [...] > > I can't tell from your original post, but are you implying slocate > never terminates? When a process exits, any resources it had > allocated are automatically returned to the kernel.
Hmmm, re-reading this one, I would say that the used memory is purely due to disk cache. I'm not sure what the 'calculation' above is meant to mean - 'used + buffers - cache'? Not that I know exactly what 'buffers' is meant to entail anyway, I would guess that figure doesn't drop down after slocate (updatedb?) finishes. -- Regards, Jason Stubbs -- [EMAIL PROTECTED] mailing list
