> total used free shared buffers cached
>Mem: 14648 14316 332 8004 4904 5200
>-/+ buffers: 4212 10436
>Swap: 17132 12 17120
available (10 megs in buffers, 332 K free already). Are you SURE you are
out of memory? Do you see kernel errors liek "cannot get free page"? The
above really does not look like your out of memory...
Or it could be an out of control process too. Im going completely by guessQuote:>While I was testing my web pages, I actually ran out of memory and the only
>thing I could do was to walk over to the server and give the three fingered
>salute. It was as if the memory wasn't being released properly. I
>installed Apache 1.2b8 and that seemed to help a little bit, the memory
>used doesn't seem to climb as quickly.
here, but I would suspect MySQL first. MySQL is not ready for production
use yet, and contains lots of bugs. It would not surprise me if that was
Are you running PHP as an apache module? If so, try running "strip" on
your httpd binary as it will contain a lot of debugging symbols by default
when you build it. THat will reduce the size of the executable by a good
What version of flex are your running? PHP has been known to have some
problems with versions of flex prior to 2.5.4 (but not the type of probs
that you seem to be having).
Id suggest killing of MySQL for a while and see if you still have the same
troubles. Try to see if you have any runaway processes next time the
machine starts to bog down (use top).
Hope this helps...
Hal 9000 - "Put down those Windows disks Dave.... Dave? DAVE!!"