On Friday 06 February 2004 00:44, John McKerrell wrote:
> > 2. Why are the servers being restarted once a day ? There shouldn't be a
> > need to restart unless something is going wrong.
>
> For cycling the logs, we've got scripts setup to sort them out each day
> - backing them up and suchlike, wh
On Thu, 2004-02-05 at 16:12, vidyut luther wrote:
> Hi John,
> A couple of questions..
> 1. Define high load.
Er.. that's quite a personal question, apparently we get 58 million hits
a month but some days will be much busier than others (we're a soccer
site, match days are busiest). The load is sp
Hi,
I've been working with a PHP for a few years now. I've always thought
that on production servers, to have them working at peak efficiency, I
should have the Apache and PHP compiled as a static build. I recently
got into a debate with someone over whether this had any worthwhile
savings. Can
Thanks very much John :)
John Nichel wrote:
It probably wouldn't help you all that much. Since it was for my own
personal use, I hardcoded directory paths and such for my personal set
up. I used to do it with a shell script too (nothing fancy there either).
Just configure it again without ap
It probably wouldn't help you all that much. Since it was for my own
personal use, I hardcoded directory paths and such for my personal set
up. I used to do it with a shell script too (nothing fancy there either).
Just configure it again without apxs
./configure --with-whateveroptions
mak
Hi John,
Can we share your Perl script?
I compiled with switch "--with-apxs=/usr/local/apache/bin/apxs"
Is it that apache switch?
Thanks
Tariq
John Nichel wrote:
I went thru the same problem, so one day I just sat down, and wrote a
Perl script that does the module and binary at the same time
I went thru the same problem, so one day I just sat down, and wrote a
Perl script that does the module and binary at the same time. Saved me
alot of grief.
Scott Hurring wrote:
If you do it correctly, yes.
The apache module usually lives somewhere in the apache hierarchy,
whereas the 'php' bin
Thanks to all that replied.
Ed
On Mon, 9 Dec 2002, John Nichel wrote:
> Yes you can. Just use clean source, but the config line can be the same
> less the "--with-apache" switch.
>
> [EMAIL PROTECTED] wrote:
> > Can I do that using the same src I used to create the dynamic module and
> >
Yes you can. Just use clean source, but the config line can be the same
less the "--with-apache" switch.
[EMAIL PROTECTED] wrote:
Can I do that using the same src I used to create the dynamic module and
both would work hapilly together?
Thanks,
Ed
On Mon, 9 Dec 2002, John Nichel wrote:
N
If you do it correctly, yes.
The apache module usually lives somewhere in the apache hierarchy,
whereas the 'php' binary is '/usr/bin/' or '/usr/local/bin/', so they
can quite happily co-exist.
Beware though, when upgrading one, upgrade BOTH.
It drove me nuts once when i forgot, and ended up havi
Can I do that using the same src I used to create the dynamic module and
both would work hapilly together?
Thanks,
Ed
On Mon, 9 Dec 2002, John Nichel wrote:
> No. To get the binary executable, compile it without the apache switch.
>
> [EMAIL PROTECTED] wrote:
> > When you compile php for
No. To get the binary executable, compile it without the apache switch.
[EMAIL PROTECTED] wrote:
When you compile php for apache using the dynamic module example used in
the documentation, do you not get an exacutable php to use from the
command line?
Ed
--
By-Tor.com
It's all about the
When you compile php for apache using the dynamic module example used in
the documentation, do you not get an exacutable php to use from the
command line?
Ed
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
13 matches
Mail list logo
