You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@perl.apache.org by Doug MacEachern <do...@covalent.net> on 2002/04/07 07:04:53 UTC
[announce] mod_perl-1.99_01
The URL
http://perl.apache.org/dist/mod_perl-1.99_01.tar.gz
has entered CPAN as
file: $CPAN/authors/id/D/DO/DOUGM/mod_perl-1.99_01.tar.gz
size: 368151 bytes
md5: 8db81a4cc572544eb427f2beb1beceea
This is the first public release of mod_perl version 2.0-tobe.
Apache version 2.0.35 or higher is required.
Perl version 5.6.0 or higher is required.
mod_perl is currently considered beta when used with the prefork MPM.
mod_perl is currently considered alpha when used with a threaded MPM.
Only DSO build of mod_perl-2.0 is currently supported, static builds
will be support in the future.
mod_perl-2.0-tobe is not 100% feature complete with the 1.xx version.
See the todo/ directory for what remains to be done.
Comments, questions, bug-reports, etc., should be sent to the mod_perl
users list: modperl@perl.apache.org.
Enjoy,
-Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: announce-unsubscribe@perl.apache.org
For additional commands, e-mail: announce-help@perl.apache.org
Disabling Perl*Handlers in .htaccess?
Posted by ka...@suvi.kas.utu.fi.
Hello!
How to enable only PerlSetVar/PerlAddVar directives in .htaccess files?
More specific:
We are building an multiuser environment with mod_perl to our
campus. Mod_perl handlers contain especially PerlHandlers configured in
httpd.conf. The .htaccess files are used for authorization (require
user/group) and some tailoring (PerlSetVar/PerlAddVar) allowed for all
users at their home directories.
However, the security risks are quite obvious when .htaccess contains
directives like PerlHandler:
PerlHandler "sub {`touch /tmp/xxx`}"
How to enable only PerlSetVar/PerlAddVar directives in .htaccess files?
--
Kari Nurmela,
kari.nurmela@utu.fi, (02) 333 8847 / (0400) 786 547
Re: mod_perl-1.99_01 make test fails
Posted by Jie Gao <J....@isu.usyd.edu.au>.
Sorry, I got the wrong version. :-(
Jie
On Tue, 9 Apr 2002, Jie Gao wrote:
> Date: Tue, 9 Apr 2002 16:25:24 +1000 (EST)
> From: Jie Gao <J....@isu.usyd.edu.au>
> To: modperl@perl.apache.org
> Subject: mod_perl-1.99_01 make test fails
>
> Hi Doug,
>
> Apache 2.0.35 + modperl_20020409042640
> uname -a:
> Linux xxx.xxx.xx.xx 2.4.18-01-shuckle #4 Fri Apr 5 12:42:54 EST 2002 i686 unknown
>
> perl -V
> Summary of my perl5 (revision 5.0 version 6 subversion 1) configuration:
> Platform:
> osname=linux, osvers=2.4.17-0.13smp, archname=i386-linux
> uname='linux daffy.perf.redhat.com 2.4.17-0.13smp #1 smp fri feb 1 10:30:48 est 2002 i686 unknown '
> config_args='-des -Doptimize=-O2 -march=i386 -mcpu=i686 -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dcccdlflags=-fPIC
> -Dinstallprefix=/usr -Dprefix=/usr -Darchname=i386-linux -Uusethreads -Uuseithreads -Uuselargefiles -Dd_dosuid
> -Dd_semctl_semun -Di_db -Di_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Dlocincpth='
> hint=recommended, useposix=true, d_sigaction=define
> usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
> useperlio=undef d_sfio=undef uselargefiles=undef usesocks=undef
> use64bitint=undef use64bitall=undef uselongdouble=undef
> Compiler:
> cc='gcc', ccflags ='-fno-strict-aliasing -I/usr/local/include',
> optimize='-O2 -march=i386 -mcpu=i686',
> cppflags='-fno-strict-aliasing -I/usr/local/include'
> ccversion='', gccversion='2.96 20000731 (Red Hat Linux 7.1 2.96-98)', gccosandvers=''
> intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
> d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
> ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=4
> alignbytes=4, usemymalloc=n, prototype=define
> Linker and Libraries:
> ld='gcc', ldflags =' -L/usr/local/lib'
> libpth=/usr/local/lib /lib /usr/lib
> libs=-lnsl -ldl -lm -lc -lcrypt -lutil
> perllibs=-lnsl -ldl -lm -lc -lcrypt -lutil
> libc=/lib/libc-2.2.4.so, so=so, useshrplib=false, libperl=libperl.a
> Dynamic Linking:
> dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
> cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib'
>
>
> Characteristics of this binary (from libperl):
> Compile-time options:
> Built under linux
> Compiled at Feb 20 2002 15:01:16
> @INC:
> /usr/lib/perl5/5.6.1/i386-linux
> /usr/lib/perl5/5.6.1
> /usr/lib/perl5/site_perl/5.6.1/i386-linux
> /usr/lib/perl5/site_perl/5.6.1
> /usr/lib/perl5/site_perl
>
> perl Makefile.PL APACHE_SRC=../apache+mod_perl/src DO_HTTPD=1 USE_APACI=1 PREP_HTTPD=1 EVERYTHING=1 PERL_TRACE=1
>
> # make test
> ...
>
> /usr/bin/perl t/TEST 0
> modules/actions.....ok
> modules/cgi.........ok
> modules/constants...ok
> modules/cookie......skipped test on this platform
> modules/embperl.....skipped test on this platform
> modules/eperl.......skipped test on this platform
> modules/file........ok
> modules/httpdconf...ok
> modules/include.....ok
> modules/log.........ok
> modules/module......skipped test on this platform
> modules/perlrun.....ok
> modules/perlrunxs...skipped test on this platform
> modules/psections...skipped test on this platform
> modules/request.....skipped test on this platform
> modules/sandwich....skipped test on this platform
> modules/src.........ok
> modules/ssi.........ok
> modules/stage.......skipped test on this platform
> modules/status......ok
> modules/symbol......skipped test on this platform
> modules/uri.........ok
> modules/util........ok
> internal/api........FAILED test 18
> Failed 1/87 tests, 98.85% okay
> internal/auth.......ok
> internal/croak......ok
> internal/dirmagic...ok
> internal/error......ok
> internal/headers....ok
> internal/hooks......ok
> internal/http-get...ok
> internal/http-post..ok
> internal/proxy......ok
> internal/redirect...ok
> internal/rwrite.....ok
> internal/stacked....ok
> internal/table......ok
> internal/taint......ok
> Failed Test Status Wstat Total Fail Failed List of Failed
> --------------------------------------------------------------------------------
> internal/api.t 87 1 1.15% 18
> 10 tests skipped.
> httpd terminated
> Failed 1/38 test scripts, 97.37% okay. 1/393 subtests failed, 99.75% okay.
> make: *** [run_tests] Error 29
>
> more t/logs//error_log
> [notice] Destruction->DESTROY called for $global_object
> Prototype mismatch: sub Socket::INADDR_ANY vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 329.
> Prototype mismatch: sub Socket::INADDR_BROADCAST vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 330.
> Prototype mismatch: sub Socket::INADDR_LOOPBACK vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 331.
> Prototype mismatch: sub Socket::INADDR_LOOPBACK vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 332.
> [Tue Apr 9 17:16:36 2002] [warn] [notice] child_init for process 2740, report any problems to [no address given]
>
> [Tue Apr 9 17:16:39 2002] [warn] [client 127.0.0.1] log __ANON__ OK
> Use of uninitialized value in subroutine entry at /export/src/modperl/t/net/perl/api.pl line 223, <fh00001b> line
> 1.
> *** The following [error] is expected, no cause for alarm ***
> [Tue Apr 9 17:16:42 2002] [error] Missing right curly or square bracket at /export/src/modperl/t/docs/badsyntax.pl
> line 9,
> at end of line
> syntax error at /export/src/modperl/t/docs/badsyntax.pl line 9, at EOF
> Compilation failed in require at /export/src/modperl/t//docs/startup.pl line 251, <fh00001b> line 1.
>
> *** The following [error] is expected, no cause for alarm ***
> [Tue Apr 9 17:16:42 2002] [error] Apache::Death at PerlHandler subroutine `Apache::Death::handler' line 1
>
> *** The following [error] is expected, no cause for alarm ***
> [Tue Apr 9 17:16:42 2002] [error] Missing right curly or square bracket at /export/src/modperl/t/docs/badsyntax.pl
> line 9,
> at end of line
> syntax error at /export/src/modperl/t/docs/badsyntax.pl line 9, at EOF
> Compilation failed in require at /export/src/modperl/t//docs/startup.pl line 251, <fh00001b> line 1.
>
> *** The following [error] is expected, no cause for alarm ***
> [Tue Apr 9 17:16:42 2002] [error] Apache::Death at PerlHandler subroutine `Apache::Death::handler' line 1
>
> [notice] child process 2740 terminating
> [notice] push'd PerlChildExitHandler called, pid=2740
> [notice] push'd PerlChildExitHandler called, pid=2740
> [notice] END block called for startup.pl
> [notice] Destruction->DESTROY called for $global_object
>
> Regards,
>
>
>
> Jie
>
>
mod_perl-1.99_01 make test fails
Posted by Jie Gao <J....@isu.usyd.edu.au>.
Hi Doug,
Apache 2.0.35 + modperl_20020409042640
uname -a:
Linux xxx.xxx.xx.xx 2.4.18-01-shuckle #4 Fri Apr 5 12:42:54 EST 2002 i686 unknown
perl -V
Summary of my perl5 (revision 5.0 version 6 subversion 1) configuration:
Platform:
osname=linux, osvers=2.4.17-0.13smp, archname=i386-linux
uname='linux daffy.perf.redhat.com 2.4.17-0.13smp #1 smp fri feb 1 10:30:48 est 2002 i686 unknown '
config_args='-des -Doptimize=-O2 -march=i386 -mcpu=i686 -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dcccdlflags=-fPIC
-Dinstallprefix=/usr -Dprefix=/usr -Darchname=i386-linux -Uusethreads -Uuseithreads -Uuselargefiles -Dd_dosuid
-Dd_semctl_semun -Di_db -Di_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Dlocincpth='
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=undef usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
Compiler:
cc='gcc', ccflags ='-fno-strict-aliasing -I/usr/local/include',
optimize='-O2 -march=i386 -mcpu=i686',
cppflags='-fno-strict-aliasing -I/usr/local/include'
ccversion='', gccversion='2.96 20000731 (Red Hat Linux 7.1 2.96-98)', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=4
alignbytes=4, usemymalloc=n, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib
libs=-lnsl -ldl -lm -lc -lcrypt -lutil
perllibs=-lnsl -ldl -lm -lc -lcrypt -lutil
libc=/lib/libc-2.2.4.so, so=so, useshrplib=false, libperl=libperl.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options:
Built under linux
Compiled at Feb 20 2002 15:01:16
@INC:
/usr/lib/perl5/5.6.1/i386-linux
/usr/lib/perl5/5.6.1
/usr/lib/perl5/site_perl/5.6.1/i386-linux
/usr/lib/perl5/site_perl/5.6.1
/usr/lib/perl5/site_perl
perl Makefile.PL APACHE_SRC=../apache+mod_perl/src DO_HTTPD=1 USE_APACI=1 PREP_HTTPD=1 EVERYTHING=1 PERL_TRACE=1
# make test
...
/usr/bin/perl t/TEST 0
modules/actions.....ok
modules/cgi.........ok
modules/constants...ok
modules/cookie......skipped test on this platform
modules/embperl.....skipped test on this platform
modules/eperl.......skipped test on this platform
modules/file........ok
modules/httpdconf...ok
modules/include.....ok
modules/log.........ok
modules/module......skipped test on this platform
modules/perlrun.....ok
modules/perlrunxs...skipped test on this platform
modules/psections...skipped test on this platform
modules/request.....skipped test on this platform
modules/sandwich....skipped test on this platform
modules/src.........ok
modules/ssi.........ok
modules/stage.......skipped test on this platform
modules/status......ok
modules/symbol......skipped test on this platform
modules/uri.........ok
modules/util........ok
internal/api........FAILED test 18
Failed 1/87 tests, 98.85% okay
internal/auth.......ok
internal/croak......ok
internal/dirmagic...ok
internal/error......ok
internal/headers....ok
internal/hooks......ok
internal/http-get...ok
internal/http-post..ok
internal/proxy......ok
internal/redirect...ok
internal/rwrite.....ok
internal/stacked....ok
internal/table......ok
internal/taint......ok
Failed Test Status Wstat Total Fail Failed List of Failed
--------------------------------------------------------------------------------
internal/api.t 87 1 1.15% 18
10 tests skipped.
httpd terminated
Failed 1/38 test scripts, 97.37% okay. 1/393 subtests failed, 99.75% okay.
make: *** [run_tests] Error 29
more t/logs//error_log
[notice] Destruction->DESTROY called for $global_object
Prototype mismatch: sub Socket::INADDR_ANY vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 329.
Prototype mismatch: sub Socket::INADDR_BROADCAST vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 330.
Prototype mismatch: sub Socket::INADDR_LOOPBACK vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 331.
Prototype mismatch: sub Socket::INADDR_LOOPBACK vs () at /usr/lib/perl5/5.6.1/i386-linux/Socket.pm line 332.
[Tue Apr 9 17:16:36 2002] [warn] [notice] child_init for process 2740, report any problems to [no address given]
[Tue Apr 9 17:16:39 2002] [warn] [client 127.0.0.1] log __ANON__ OK
Use of uninitialized value in subroutine entry at /export/src/modperl/t/net/perl/api.pl line 223, <fh00001b> line
1.
*** The following [error] is expected, no cause for alarm ***
[Tue Apr 9 17:16:42 2002] [error] Missing right curly or square bracket at /export/src/modperl/t/docs/badsyntax.pl
line 9,
at end of line
syntax error at /export/src/modperl/t/docs/badsyntax.pl line 9, at EOF
Compilation failed in require at /export/src/modperl/t//docs/startup.pl line 251, <fh00001b> line 1.
*** The following [error] is expected, no cause for alarm ***
[Tue Apr 9 17:16:42 2002] [error] Apache::Death at PerlHandler subroutine `Apache::Death::handler' line 1
*** The following [error] is expected, no cause for alarm ***
[Tue Apr 9 17:16:42 2002] [error] Missing right curly or square bracket at /export/src/modperl/t/docs/badsyntax.pl
line 9,
at end of line
syntax error at /export/src/modperl/t/docs/badsyntax.pl line 9, at EOF
Compilation failed in require at /export/src/modperl/t//docs/startup.pl line 251, <fh00001b> line 1.
*** The following [error] is expected, no cause for alarm ***
[Tue Apr 9 17:16:42 2002] [error] Apache::Death at PerlHandler subroutine `Apache::Death::handler' line 1
[notice] child process 2740 terminating
[notice] push'd PerlChildExitHandler called, pid=2740
[notice] push'd PerlChildExitHandler called, pid=2740
[notice] END block called for startup.pl
[notice] Destruction->DESTROY called for $global_object
Regards,
Jie
Re: [announce] mod_perl-1.99_01
Posted by Stas Bekman <st...@stason.org>.
John Siracusa wrote:
> On 4/8/02 2:41 AM, Stas Bekman wrote:
>
>>I've searched google, but didn't find any info regarding Term::ANSIColor
>>and suggesting good cross-platform, cross-terminal colors.
>
>
> Maybe I didn't understand the earlier part of your message, but can't you
> specify both the foreground and the background color of text? It'd be ugly,
> but if you specified both you could be (relatively) sure the colors would
> show up.
Try it. The results are ugly.
> If you really want to be safe, you can use an old-style attention-grabbing
> technique like this:
>
> ********** ################## **********
> WARNING!!!!!!!
> ********** ################## **********
>
> blah blah blah
>
> ********** ################## **********
> WARNING!!!!!!!
> ********** ################## **********
well, yes, if we don't figure out how to keep the color and have people
happy, we will need to do something like that. But it'll make the output
even longer :(
Also there is an alternative way, try runnning with
APACHE_TEST_NO_COLOR=1 perl Makefile.PL
this is a poor man's version of non-coloured, but still distinguishable
printing.
> People will see stuff like that :) Or you could take the high road and just
> print it normally. As long as it's the last thing printed (i.e. It doesn't
> scroll by while they're away or in another window), people will probably
> read it :) And if not, it could be argued that they get what they deserve
> ;)
Sure, but those people end up asking questions here :). And it takes a
few emails before you figure out that they had a warning and ignored it.
So if we can make these stand out, that would save a lot of time to
everybody.
Hmm, should we beep on every error? :)
beep; beep; beep; ...; beep() x 100;
;)
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [announce] mod_perl-1.99_01
Posted by John Siracusa <si...@mindspring.com>.
On 4/8/02 2:41 AM, Stas Bekman wrote:
> I've searched google, but didn't find any info regarding Term::ANSIColor
> and suggesting good cross-platform, cross-terminal colors.
Maybe I didn't understand the earlier part of your message, but can't you
specify both the foreground and the background color of text? It'd be ugly,
but if you specified both you could be (relatively) sure the colors would
show up.
If you really want to be safe, you can use an old-style attention-grabbing
technique like this:
********** ################## **********
WARNING!!!!!!!
********** ################## **********
blah blah blah
********** ################## **********
WARNING!!!!!!!
********** ################## **********
People will see stuff like that :) Or you could take the high road and just
print it normally. As long as it's the last thing printed (i.e. It doesn't
scroll by while they're away or in another window), people will probably
read it :) And if not, it could be argued that they get what they deserve
;)
-John
Re: [announce] mod_perl-1.99_01
Posted by Ed Grimm <ed...@tgape.org>.
On Mon, 8 Apr 2002, Stas Bekman wrote:
> Ged Haywood wrote:
>> Compilations should be SILENT unless something goes wrong.
>
> The build process takes time, if you don't give an indication
> of what's going on users will try to do funky things. Since the
> build process is comprised of many small sub-processes you cannot
> really use something like completion bar.
As someone said, redirect the output to a temporary location. But, add
to that one of those little | bars, which turns one position every time
another build step completes (each file compiled, each dependancy file
built, etc.). However, in the case of an error, I would want the whole
thing available. Possibly something along the lines of, the last build
step and all output from then on printed to stdout (or stderr), ended
with, "For the full build log, see /tmp/mod_perl.build.3942" or some
such.
> Also remember that mod_perl build prints very little,
> it's the compilation messages that generated most of the output.
> p.s. I don't recall seeing silent build processes at all.
The only ones I've seen went too far the other way. I especially loved
the one which used a shell script, which started out with a dozen large
shell functions, then an 'exec >/dev/null 2>/dev/null', then a
half-dozen more large shell functions, and ending with 'main "$@"'.
When the shell script finished, its caller checked its exit code, and
reported 'done.' or 'failed.' as appropriate. Admittedly, I wouldn't
have minded too much, except that I'd gotten the latter answer.
Ed
Re: [announce] mod_perl-1.99_01
Posted by Stas Bekman <st...@stason.org>.
Ged Haywood wrote:
> Hi Stas,
>
> On Mon, 8 Apr 2002, Stas Bekman wrote:
>
>
>>John Siracusa wrote:
>>
>>>downside (see attached screenshot).
>>
>>the idea was to make certain messages more outstanding
>
>
> Then print only the messages you want people to see. In my view there
> is far too much output from a typical build and install (of anything:).
>
> Compilations should be SILENT unless something goes wrong.
The build process takes time, if you don't give an indication
of what's going on users will try to do funky things. Since the
build process is comprised of many small sub-processes you cannot
really use something like completion bar.
Also remember that mod_perl build prints very little,
it's the compilation messages that generated most of the output.
p.s. I don't recall seeing silent build processes at all.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [announce] mod_perl-1.99_01
Posted by Kee Hinckley <na...@somewhere.com>.
At 9:18 AM +0100 4/8/02, Ged Haywood wrote:
>Then print only the messages you want people to see. In my view there
>is far too much output from a typical build and install (of anything:).
I have to agree with this. Installers are notorious for this, with
compilers following close behind. I remember once (a long long time
ago) when I was working in the computer center in college and someone
couldn't figure out why their program wouldn't run. They'd been
compiling, editing, and running it for an hour, but it just wouldn't
run. The compiler put out about five lines of copyright and random
info everytime it ran. They didn't notice the one line of error
message that followed that.
All that diagnostic stuff is useful if something goes wrong, but not
otherwise. I like some of the newer installers now that at the end
of the run tell you exactly what directories things were installed
with, instead of asking you to peruse several pages of output. I'd
say do this:
Dump all your informative info to a variable or tmp file. If there's
an error--print the informative stuff *then*, along with the error
(or an error message and pointer to the tmp file). If there
isn't--print a nice summary and toss the variable out.
If you've got sub-builds and the like, then print a message when they
start, and print a "." for every compile as you (invisibly) see the
output go by. And of course you can erase the line and show the next
build in the same place.
--
Kee Hinckley - Somewhere.Com, LLC
http://consulting.somewhere.com/
nazgul@somewhere.com
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.
Re: [announce] mod_perl-1.99_01
Posted by Ged Haywood <ge...@www2.jubileegroup.co.uk>.
Hi Stas,
On Mon, 8 Apr 2002, Stas Bekman wrote:
> John Siracusa wrote:
> > downside (see attached screenshot).
>
> the idea was to make certain messages more outstanding
Then print only the messages you want people to see. In my view there
is far too much output from a typical build and install (of anything:).
Compilations should be SILENT unless something goes wrong.
73,
Ged.
Re: [announce] mod_perl-1.99_01
Posted by Stas Bekman <st...@stason.org>.
John Siracusa wrote:
> You might want to reconsider the use of VT escape codes in the build
> process. The red error message was cute, but there's a big potential
> downside (see attached screenshot).
>
> In the words of the W3C's CSS validator: "You have no background-color with
> your color" :)
sigh :(
the idea was to make certain messages more outstanding, so people
will pay attention to warnings and errors. In your examples warnings
are not really seen on certain terminals, which is worse than using the
default fg color.
I've tried using on_white for bg and the results are bad.
Currently we use:
%colors = (
emerg => 'bold white on_blue',
alert => 'bold blue on_yellow',
crit => 'reverse',
error => 'bold red',
warning => 'yellow',
notice => 'green',
info => 'cyan',
debug => 'magenta',
reset => 'reset',
todo => 'underline',
);
I've changed my gnome-terminal prefs to use black as bg and white as fg,
and it was pretty much OK with the current colours, darker colours being
less visible.
I guess what's important is to have at least 2 additional to the default
colors for warnings and errors. It seems that 'bold red' will be
perfectly seen on pretty much any background (but red :). Apparently
yellow is not a good choice. Any better suggestions for cross background
fg color? refer to the Term::ANSIColor manpage for more options.
Please play with
Apache-Test/lib/Apache/TestTrace.pm and see if you can come up with a
better solution.
I've searched google, but didn't find any info regarding Term::ANSIColor
and suggesting good cross-platform, cross-terminal colors.
Thanks.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [announce] mod_perl-1.99_01
Posted by John Siracusa <si...@mindspring.com>.
You might want to reconsider the use of VT escape codes in the build
process. The red error message was cute, but there's a big potential
downside (see attached screenshot).
In the words of the W3C's CSS validator: "You have no background-color with
your color" :)
-John