They aren't running PostgreSQL. Your fix is pretty drastic. If you ran Top with the M option, did you see a program using up the memory?
Christopher Maujean ([EMAIL PROTECTED]) wrote*: > >PostgreSQL used to have a memory leak that would take all 2gigs of ram >from my machine. I wrote a perl script that filled an array with 'A''s >infinitely, until it ran out of memory once it crashed, it gave all that >memory back. Ran it as a cron job every half hour. > > >On Thu, 2001-12-20 at 09:12, Bob Crandell wrote: >> That shows how much memory each program is using but it doesn't add up to the amount >> of memory being used. There is over a half Gig of RAM and 96 M of swap. It all >> gets used up just before it goes down. >> >> Is there another utility? >> >> Thanks >> >> Bob Miller ([EMAIL PROTECTED]) wrote*: >> > >> >Bob Crandell wrote: >> > >> >> I have a client with a Linux server running Samba. Something is >> >> filling up memory and the swap space. This is dragging down to the >> >> point where it's unusable. They have to reboot almost every day. >> >> >> >> My question is how do I find out what is taking up all that memory? >> > >> >Run top, then type "M" (capital M). Watch the size column. >> > >> > >> > > >PGP: >--------------------------------------------------------------- >http://www.keyserver.net/ >KeyID: EFAF4176 >Fingerprint: 55E6 4DE1 D7D3 361E F265 C094 46F2 7B62 EFAF 4176 >--------------------------------------------------------------- > >
