according to this page
http://httpd.apache.org/docs/current/mod/core.html Linux on Itanium
CPU cannot handle files over 2GB
regards,
Frédéric
On 9 August 2010 23:28, Li N lin@gmail.com wrote:
Hi everyone,
One of the new features of Apache2.2 is Large File Support, and it could
support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/10 18:22, Hélène Montarou wrote:
Hi,
I have installed httpd-2.2.3 and I would like to generate a certificate.
The machine on which it is installed has an internal name
(internal.domain.com) and I would like to use another name for
We have installed apache(Apache/2.2.10) and we have a .pl file that is being
loaded in httpd.conf.
When we are trying to restart the server, We receive the following error :
[Tue Aug 10 11:34:31 2010] [error] Can't locate ARS.pm in @INC (@INC
contains: /opt/app/ars/ovsc/perl
On 10 Aug 2010, at 08:11, Frédéric SOSSON wrote:
according to this page
http://httpd.apache.org/docs/current/mod/core.html Linux on Itanium
CPU cannot handle files over 2GB
No it doesn't. It notes a limitation of sendfile, and (without knowing who
wrote that line and what they checked) I'd
On Aug 10, 2010, at 5:49 AM, aparna aryan wrote:
We have installed apache(Apache/2.2.10) and we have a .pl file that
is being loaded in httpd.conf.
When we are trying to restart the server, We receive the following
error :
[Tue Aug 10 11:34:31 2010] [error] Can't locate ARS.pm in @INC
Hi,
is there any way how to load 32bit module to 64bit httpd 2.2?
Reason for asking such weird question, vendor is providing 3th party
module only as 32bit version. I have all my web servers as 64bit. Because of
count of servers (more than several hundreds), I don't like to start support
32bit
On Aug 10, 2010, at 5:50 AM, Nick Kew wrote:
On 10 Aug 2010, at 08:11, Frédéric SOSSON wrote:
according to this page
http://httpd.apache.org/docs/current/mod/core.html Linux on Itanium
CPU cannot handle files over 2GB
No it doesn't. It notes a limitation of sendfile, and (without
I'm thinking about trying to upgrade to 2.2.16 to fix this issue, but
not sure it will help. I see that 2.2.10 had one fix:
*) mod_proxy_http: Do not forward requests with 'Expect: 100-continue'
to
known HTTP/1.0 servers. Return 'Expectation failed' (417) instead.
[Ruediger Pluem]