On 19.06.2011, at 23:00, DW wrote:
> sunhux G wrote:
>> After making changes to httpd.conf, can I just issue
>>
>> 1) "kill -HUP httpd_instance_pid" for the change to take effect or
>> 2) "service httpd reload" or
>> 3) "service httpd restart"
>>
>> Select one or more of the above correct opt
On 6/19/2011 5:44 AM, Nathan Tuggy wrote:
> Just upgraded from 2.2.10 to 2.2.19 [*], and Windows service won't start --
> it gives me
> two lines in the error log (LogLevel is set to debug) claiming that it's
> starting up:
>
> Starting the Apache2.2 service
> The Apache2.2 service is ru
On 06/20/2011 02:38 AM, Zaccone, Warren wrote:
Runningmultiple copies of this script concurrently brings httpd into a
hang state, that it will not recover from without manually restarting
the httpd server.
ab-n 300 -c 300 http://myserver/mysite/loop.php
You're requesting a single URL 300
> I have timeout set to 900 but it does not appear to be working. What does
> timeout in the httpd.conf do?
http://httpd.apache.org/docs/current/mod/core.html#timeout
> Will the httpd.conf timeout protect the server from such scripts or is
> there something else.
Not malicious ones, perhaps s
Running multiple copies of this script concurrently brings httpd into a hang
state, that it will not recover from without manually restarting the httpd
server.
ab -n 300 -c 300 http://myserver/mysite/loop.php
I have timeout set to 900 but it does not appear to be working. What does
timeout
On 2011-06-19 14:05, Robert Hall wrote:
On Jun 19, 2011, at 1:56 PM, DW wrote:
Nathan Tuggy wrote:
Just upgraded from 2.2.10 to 2.2.19 [*], and Windows service won't
start
-- it gives me two lines in the error log (LogLevel is set to debug)
claiming that it's starting up:
Starting the Ap
On Jun 19, 2011, at 1:56 PM, DW wrote:
Nathan Tuggy wrote:
Just upgraded from 2.2.10 to 2.2.19 [*], and Windows service won't
start
-- it gives me two lines in the error log (LogLevel is set to debug)
claiming that it's starting up:
Starting the Apache2.2 service
The Apache2.2 service
Before you make any changes to the configuration file, you must stop the
apache service otherwise you won't be able to save your changes.
Then when the changes are made and the file is saved, you need to start
the apache service for all changes to take effect.
Hope this helps.
sunhux G wrote:
The way I upgraded to 2.2.19 was first copying my configuration file
somewhere safe; then uninstalling apache from the servers; then start a
fresh install of apache 2.2.19. You then need to copy your old
configuration file back to the server so that you don't need to waste
any more time.
Caveat
After making changes to httpd.conf, can I just issue
1) "kill -HUP httpd_instance_pid" for the change to take effect or
2) "service httpd reload" or
3) "service httpd restart"
Select one or more of the above correct options
Thanks
Sun
-
On 2011-06-19 04:31, Igor Galić wrote:
- Original Message -
Just upgraded from 2.2.10 to 2.2.19 [*], and Windows service won't
start
-- it gives me two lines in the error log (LogLevel is set to debug)
claiming that it's starting up:
Starting the Apache2.2 service
The Apache
- Original Message -
> Just upgraded from 2.2.10 to 2.2.19 [*], and Windows service won't
> start
> -- it gives me two lines in the error log (LogLevel is set to debug)
> claiming that it's starting up:
>
> Starting the Apache2.2 service
> The Apache2.2 service is running.
>
> T
Just upgraded from 2.2.10 to 2.2.19 [*], and Windows service won't start
-- it gives me two lines in the error log (LogLevel is set to debug)
claiming that it's starting up:
Starting the Apache2.2 service
The Apache2.2 service is running.
Then it silently dies.
Running httpd from the
13 matches
Mail list logo
