Am Tue, 26 Aug 2003 16:07:21 + schrieb Stas Bekman:
As you posted in the followup, this is a problem with all Apache:: modules.
The problem originates within Apache, not us.
Didn't know that apache rejects to run as root. Strange (but safe) behaviour.
Ideas how to solve this are *very*
hi all,
I'm trying to setup Apache::Test with our apaches and have run into major
troubles.
CPAN refuses to install the mod without force, because all tests completely
fail. t/logs/error_log then contained error messages like these:
-error_log--
[...]
[Tue Aug 26 14:23:47 2003]
hmm, and as I just found out, the same applies for many other Apache:: mods
(libapreq ...)
This looks like a major problem to me.
Temporary workaround is to give read access to all users for ~root, but
that makes me a bit nervous ...
udo
--
Reporting bugs: http://perl.apache.org/bugs/
Am Sat, 23 Aug 2003 09:48:05 + schrieb B. Fongo:
foreach (@table_data)
{
print qq(td bgcolor='#d0d0d0'$_/td); # Here is line 42
}
as Frank already pointed out, your trouble is the uninitialized $_ value
you have in line 42 (which is exactly what
=$RPM_BUILD_ROOT/usr/somedir make install
and
% make PREFIX=$RPM_BUILD_ROOT/usr/somedir install
... but it completely ignores the (temporary) PREFIX for the
installation.
So are there any (make) switches to temporarily override the installation
directory for mod_perl 1.2.x??
Thanks
Udo Rader
--
Reporting
(in Makefile.PL)?
udo
Am Fri, 22 Aug 2003 11:50:44 + schrieb Udo Rader:
hi all,
for one of our webprojects I have to setup the typical
apache1-mod_perl-mod_ssl httpd, which is not too difficult. Our sysadmin
rules however require me to set this up as _one_ nice RPM package, which
should
Am Fri, 22 Aug 2003 17:34:40 + schrieb Stas Bekman:
Udo Rader wrote:
hi all,
for one of our webprojects I have to setup the typical
apache1-mod_perl-mod_ssl httpd, which is not too difficult. Our sysadmin
rules however require me to set this up as _one_ nice RPM package, which
should
hi,
I've been trying to post this error before, but somehow it did not make it
to the list, so I'm trying once again ...
As I saw, the new 1.99_08 version of mod_perl has $r-read fixed now to
correctly read the given bytes.
hi,
I see that the new version of mod_perl has $r-read fixed now to read
exactly the given bytes.
$r-get_client_block however is still buggy. If for example I do the
following:
CUT
my $len = $r-headers_in-{'content-length'};
print reported length is $lenbr;
my $buf;
s/[^/]+/[a-zA-Z0-9][a-zA-Z0-9_]*):) {
$cmd .= " --activate-module=$1";
}
elsif(/([a-zA-Z0-9][a-zA-Z0-9_]*)/) {
$cmd .= " --enable-module=$1";
}
... which results in a successful build.
greets
Udo Rade
10 matches
Mail list logo
