Thank for responce.
the php is installed as CGI-BIN executable. I think "keep the connections
open" option is not applicable here. I do this because every user works
under its own uid and gid, instead all under "nobody".
i dont have any idea what lsof is...
I will try with netstat, but I was used "ps -axef" and "top".
---------------
p.p.
can you told me also how I can use ulimit to limit all postmaster children's
memory ? I mean can i "say" lets all pg uses 40 MB RAM (postmaster and
children)
Nikolay Mijaylov
--------------------------------------------------------------
The reboots are for hardware upgrades!
"http://www.nmmm.nu"; < nmmm@nmmm.nu >
-----Original Message-----
From: pgsql-general-owner@hub.org [mailto:pgsql-general-owner@hub.org]On
Behalf Of Gunnar R|nning
Sent: Thursday, October 05, 2000 4:35 PM
To: Nikolay Mijaylov
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] FW: URGENT: pgsql on the web server - memory
problems....
"Nikolay Mijaylov" <pg@nmmm.nu> writes:
> The problem is that PHP is auto killing after a while (1-2 min), but the
pos
> tgres backend process stay (and works about 2 or many more hours). Soon
all
> Linux is filled with 64 postgres processes, free memory is 0 and Linux,
free
> ze :)
>
The postgres backend processes should die when the connections are
closed. Are you sure that the process that runs PHP doesn't keep the
connections open ? You should check open ports using netstat -a and maybe
go on using lsof to check the client processes.
regards,
Gunnar
