Good Morning Stas.

On Tue, 2003-12-16 at 21:33, Stas Bekman wrote:
> Stas Bekman wrote:
> I think I've figured it out. Can you please try with the current cvs or just 
> apply this patch:
> 

This is the result after updating from CVS:

/usr/bin/perl -Iblib/arch -Iblib/lib \
t/TEST -clean
*** setting ulimit to allow core files
ulimit -c unlimited; t/TEST -clean
APACHE_USER= APACHE_GROUP= APACHE_PORT= APACHE= APXS= \
/usr/bin/perl -Iblib/arch -Iblib/lib \
t/TEST -bugreport -verbose=0 
*** setting ulimit to allow core files
ulimit -c unlimited; t/TEST -bugreport -verbose=0
*** root mode: changing the files ownership to 'nobody' (99:99)
*** testing whether 'nobody' is able to -rwx /root/modperl-2.0/t
/usr/bin/perl -Mlib=/root/modperl-2.0/Apache-Test/lib -MApache::TestRun
-e 'eval
 { Apache::TestRun::run_root_fs_test(99, 99, q[/root/modperl-2.0/t]) }';


*** result: 
!!! You are running the test suite under user 'root'.
Apache cannot spawn child processes as 'root', therefore
we attempt to run the test suite with user 'nobody' (99:99).
The problem is that the path (including all parent directories):
  /root/modperl-2.0/t
must be 'rwx' by user 'nobody', so Apache can read and write under that
path.

There are several ways to resolve this issue. One is to move and
rebuild the distribution to '/tmp/' and repeat the 'make test'
phase. The other is not to run 'make test' as root (i.e. building
under your /home/user directory).

You can test whether some directory is suitable for 'make test' under
'root', by running the following test:
  % /usr/bin/perl -Mlib=/root/modperl-2.0/Apache-Test/lib
-MApache::TestRun -e '
eval { Apache::TestRun::run_root_fs_test(99, 99, q[/root/modperl-2.0/t])
}';

from that directory.


+--------------------------------------------------------+
| Please file a bug report: http://perl.apache.org/bugs/ |
+--------------------------------------------------------+
make: *** [run_tests] Error 255

Regards
Volker


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to