[nycphp-talk] PHP server app
Mark Armendariz
nyphp at enobrev.com
Sat May 8 23:24:23 EDT 2004
Well ,I'm definitely interested, but nowhere near well schooled enough on
the subject. I've been reading quite a bit on it lately (thanks mostly to
all the input I've received from a bunch of you). I have posix on my
server, but unfortunately not pcntl. I can probably request it, but I
figure I should set up something local for such a thing before putting it on
my remote server.
> -----Original Message-----
> From: talk-bounces at lists.nyphp.org
> [mailto:talk-bounces at lists.nyphp.org] On Behalf Of Hans Zaunere
> Sent: Saturday, May 08, 2004 9:16 PM
> To: NYPHP Talk
> Subject: RE: [nycphp-talk] PHP server app
>
>
> > > > Anyone have experience running a constantly running
> 'server' app
> > > > based on php from a linux server?
> > ....
> > > Memory leaks may be a problem. You can certainly do it but be
> > > prepared to restart the thing daily.
> >
> > How about using a super daemon like Inetd to call the program on
> > demand instead of having it up all the time. Should have some
> > performance degradation, but would solve the memory leak problem.
>
> This would make a very interesting article in the upcoming AMPeers.
>
> I've run PHP daemons for some time (we're talking several
> weeks) without any indication of memory leaks. In fact, I
> even coded a timer in to email me stats of the process so
> that I could keep an eye on it. At the end of a couple
> weeks, I brought the process down normally, and all seemed good.
>
> In fact, I'm looking to deploy another daemon in PHP. This
> one will accept considerable network traffic from a remote
> sensor (using FUID I believe it will be) and then manipulate
> an inline Apache PHP via MySQL for web page generation (yeah,
> it's crazy; it's an art project).
>
> H
>
> _______________________________________________
> talk mailing list
> talk at lists.nyphp.org
> http://lists.nyphp.org/mailman/listinfo/talk
>
>
>
More information about the talk
mailing list