Re: choice of mod_perl technology for news site

[Matt Sergeant]

On Wed, 6 Feb 2002, Drew Taylor wrote:

> You should take a look at Bricolage (http://bricolage.thepirtgroup.com/).
> It's a relatively new, but comprehensive, CMS that is based on Mason &
> mod_perl. I think it supports most of the things you mentioned below, but
> you should ask the developers to be sure.
>
> If you talk w/ Matt, he'll be sure to hawk AxKit. But then that's Matt. And
> AxKit really is cool stuff. :-)

Well I'd rather recommend whatever works for people. Bricolage certainly
seems full featured, and it looks easy enough to add XSLT support to it,
though I haven't had chance to download and try that yet.

As far as AxKit based CMS's go, well I was writing one but it died in the
dot-bomb as I became an "Anti Spam and Virus Technologist" (which is
actually a really nice change from web hacking). As far as other CMS's,
Robin has already mentioned XIMS and his Tesserra, but forgot about this
one: http://www.callistocms.com/ which simply blew my mind looking at the
graphics. I guess I'm easily pleased ;-) I don't know if that one is going
to be free or not though.

-- 

<:->Get a smart net

Re: choice of mod_perl technology for news site

[Robin Berjon]

On Thursday 07 February 2002 02:06, Nate Campi wrote:
> I like Mason's way of doing things, and it works for salon.com (similar
> needs), but now that we have AxKit, is that the right way to go? Seems
> better to force the separation of content and display, and using XML
> allows the stories to be easily shared for display on affiliated sites.
>
> Thoughts?

Die Vignette, die !! I'm all with you on that one ;-)

If you like the Mason way, you might want to check out Bricolage, which has 
some of the feature you wish for (but not all at this point). I haven't 
played with it extensively as of now, but it certainly looks nice.

If you want AxKit, there are CMSs is being built there. I haven't checked out 
XIMS in a while, and last time I heard it was running under 
CGI::XMLApplication / SAWA but considered to be easily portable to AxKit. I 
don't know where it is now, and how soon it will be publicly available.

The other AxKit CMS being built (that I know of) is Tessera. Tessera however 
has no planned release date. It's a CMS I'm building, and that will happen. 
But I have no intention to hurry through it as I want to get it right. I have 
code all over the place, but I don't intend to release anything until I have 
a working core that I'm happy with. I do believe that /on paper/ I've solved 
the issues I have with all other CMSs but that still needs to be proven by a 
fully operational software. And well, I'm "slightly" biased ;-) I plan to 
have a release by mid-March. That release, however, will not contain any GUI 
editor, just the core classes. So if you're interested by that CMS, it could 
be a while before it's there.

Depending on what you want there are very nice bricks out there. Barrie 
Slaymaker has a very good module for workflows (StateML). DAV had its own set 
of modules which'll deal with a fair part of metadata. Gerald Richter was 
talking about Perl-enabling mod_dav, which would simply rock. Subversion -- 
the ultimate replacement for CVS -- is DAV based so that it should be rather 
easy to extend the current DAV module to support its versioning capabilities. 
AxKit has pipelines which can make auth and the such pluggable instead of 
builting as they are altogether too often (always?) built in. It also has 
Providers and other facilities to grab content from any kind of source.

If you have a requirements document (and perhaps a timeline) I'd love to help 
you, I think I'll write a synthetic paper about Perl CMSs and content 
management in Perl in general one of these days.

-- 
___
Robin Berjon <[EMAIL PROTECTED]> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
---
Paranoids are people, too; they have their own problems.  It's easy
to criticize, but if everybody hated you, you'd be paranoid too.

Re: choice of mod_perl technology for news site

[Drew Taylor]

You should take a look at Bricolage (http://bricolage.thepirtgroup.com/). 
It's a relatively new, but comprehensive, CMS that is based on Mason & 
mod_perl. I think it supports most of the things you mentioned below, but 
you should ask the developers to be sure.

If you talk w/ Matt, he'll be sure to hawk AxKit. But then that's Matt. And 
AxKit really is cool stuff. :-)

Drew

At 05:06 PM 2/6/2002 -0800, Nate Campi wrote:
>Lets pretend I work for Wired News, and I really really hate Vignette's
>content management system. I mean *really* hate it. I'm the Ops guy
>supporting it and I have nightmares about the next unexplained CMS
>crash.
>
>Ok, we all know mod_perl is the right choice to replace their system,
>but what is the right way to go when you have a full news staff with
>many stories going out six days a week, and about a million hits a day?
>
>You need all the workflow tools for the news staff, versioning, stories
>going live at defined times and dates, etc, etc. I don't have the exact
>requirements, as I'm just trying to collect my thoughts right now, to
>bring my ideas to the software guys in a couple days. I can get the
>exact requirements if needed.
>
>I like Mason's way of doing things, and it works for salon.com (similar
>needs), but now that we have AxKit, is that the right way to go? Seems
>better to force the separation of content and display, and using XML
>allows the stories to be easily shared for display on affiliated sites.
>
>Thoughts? I'm thinking of even donating my mediocre coding skills if
>they take my advice on this - die Vignette!! I'll do my part to slay the
>evil beast.
>
>Oh, I mean if this wasn't all hypothetical - I wouldn't discuss internal
>issues like this with the general public ;)
>--
>Nate
>
>"Usenet isn't a right. It's a right, a left, and a swift uppercut to the
>jaw."  -Computer Museum (Boston)

Drew Taylor JA[P|m_p|SQL]H
http://www.drewtaylor.com/  Just Another Perl|mod_perl|SQL Hacker
mailto:[EMAIL PROTECTED]  *** God bless America! ***

choice of mod_perl technology for news site

[Nate Campi]

Lets pretend I work for Wired News, and I really really hate Vignette's
content management system. I mean *really* hate it. I'm the Ops guy
supporting it and I have nightmares about the next unexplained CMS
crash.

Ok, we all know mod_perl is the right choice to replace their system,
but what is the right way to go when you have a full news staff with
many stories going out six days a week, and about a million hits a day?

You need all the workflow tools for the news staff, versioning, stories
going live at defined times and dates, etc, etc. I don't have the exact
requirements, as I'm just trying to collect my thoughts right now, to
bring my ideas to the software guys in a couple days. I can get the
exact requirements if needed.

I like Mason's way of doing things, and it works for salon.com (similar
needs), but now that we have AxKit, is that the right way to go? Seems
better to force the separation of content and display, and using XML
allows the stories to be easily shared for display on affiliated sites.

Thoughts? I'm thinking of even donating my mediocre coding skills if
they take my advice on this - die Vignette!! I'll do my part to slay the
evil beast.

Oh, I mean if this wasn't all hypothetical - I wouldn't discuss internal
issues like this with the general public ;)
-- 
Nate

"Usenet isn't a right. It's a right, a left, and a swift uppercut to the
jaw."  -Computer Museum (Boston)  

Re: [Q] SIGSEGV After fork()

[Ged Haywood]

Hi there,

On Wed, 6 Feb 2002, Mark P. Fister wrote:

> Collectively, we've been at this for more than two weeks and have searched
> various mod_perl archives, all to no avail.

:(

> SIGSEGV after fork().  Very reproducible.  Memory corruption gets moved
> around if the codebase changes.
[snip]
> Perl:
[snip]
>   config_args='-des -Doptimize=-g -Dusedevel -Uinstallusrbinperl 
>-Ubincompat5005 -Uusemymalloc -Dcc=gcc -pipe -g -I/usr/include/db3 -Dcccdlflags=-fPIC 
>-Dinstallprefix=/home/mfister/vendor/perl-5.6.1 
>-Dprefix=/home/mfister/vendor/perl-5.6.1 [EMAIL PROTECTED] 
>-Dinstallman1dir=/home/mfister/vendor/perl-5.6.1/man/man1 
>-Dinstallman3dir=/home/mfister/vendor/perl-5.6.1/man/man3 
>-Dman1dir=/home/mfister/vendor/perl-5.6.1/man/man1 
>-Dman3dir=/home/mfister/vendor/perl-5.6.1/man/man3 -Dd_dosuid=n -Dd_semctl_semun 
>-Di_db -Di_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Uuselargefiles'

You might try usemymalloc.

> Compiler:
>   optimize='-g',

H...

>   ccversion='', gccversion='2.96 2731 (Red Hat Linux 7.1 2.96-85)', 
>gccosandvers=''

You've obviously read the docs, so I take it the same compiler built
Aapche, mod_perl and Perl.  Have you tried this on RH6.2 with the
compiler that came with that?

> Stack Trace:
> ===
> #0  __pthread_mutex_lock (mutex=0x8bf04999) at mutex.c:99
> #1  0x401b9cc8 in __libc_free (mem=0x4046cc18) at malloc.c:3152
> #2  0x403ce028 in Perl_safesysfree (where=0x4046cc18) at util.c:158
> #3  0x403f20d8 in Perl_sv_clear (sv=0x8198f60) at sv.c:3827
> #4  0x403f2473 in Perl_sv_free (sv=0x8198f60) at sv.c:3950
> #5  0x403f80e1 in do_clean_all (sv=0x8198f60) at sv.c:8411
> #6  0x403e9c5e in S_visit (f=0x403f8094 ) at sv.c:162
> #7  0x403e9ce2 in Perl_sv_clean_all () at sv.c:193
> #8  0x4038594a in perl_destruct (my_perl=0x809a9a8) at perl.c:665
> #9  0x4035629c in perl_shutdown (s=0x0, p=0x0) at mod_perl.c:294
> #10 0x40356be6 in mp_dso_unload (data=0x808e714) at mod_perl.c:489

Have you tried a statically linked mod_perl?

73,
Ged.

Can't locate Sybase/CTlib.pm

[Ng, Lynne (Exchange)]

Hi..
I got a problem when I run a test perl script. I 'm not sure that I pointed
to the right path.
Here's my script:
#!/usr/bin/perl -I
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/Sybase:/usr/local/lib/perl
5/site_perl/5.005/sun4-solaris/auto/Sybase
use Sybase::CTlib;
@INC = @lib::ORIG_INC;
print "Hello world";

It showed this error:
Can't locate Sybase/CTlib.pm in @INC

Would you please help?
Thank you very much




***
Bear Stearns is not responsible for any recommendation, solicitation, 
offer or agreement or any information about any transaction, customer 
account or account activity contained in this communication.
***

[BUG] Can't use parameters-refernces in $r->print using Apache::Filter

[Gregory Belenky]

One of the $r->print()'s declared abilities is to pass reference in place of
scalar value (to prevent "unneeded copying of large strings").

But when I use Apache::Filter and pass my output to another handler (module)
I can't use this feature.
IMHO that's because Apache::Filter->print uses

print STDOUT @_

in place of

print STDOUT ref $_ ? $$_ : $_ foreach (@_)

Am I right or what?
Dirty hack on Apache::Filter sources solved the problem.

P.S.
$Apache::Filter::VERSION == '1.019'

[Q] SIGSEGV After fork()

[Mark P. Fister]

Dear mod_perl experts:

Collectively, we've been at this for more than two weeks and have searched
various mod_perl archives, all to no avail.

Symptom:
===
SIGSEGV after fork().  Very reproducible.  Memory corruption gets moved
around if the codebase changes.

Tried:
=
* disable rule: EXPAT
* gdb
* strace -f
* MOD_PERL_TRACE=all

***NOTE***

Read no further unless you're interested in helping, since the rest is
debug/more info.

Thanks! :)











Software:

Linux:
-
2.4.13-ac5-20011101-1 #1 SMP Thu Nov 1 16:07:19 CST 2001 i686 unknown
Apache:
--
Server version: Apache/1.3.23 (Unix)
Server built:   Feb  5 2002 22:16:11
Server's Module Magic Number: 19990320:11
Server compiled with
 -D HAVE_MMAP
 -D HAVE_SHMGET
 -D USE_SHMGET_SCOREBOARD
 -D USE_MMAP_FILES
 -D HAVE_FCNTL_SERIALIZED_ACCEPT
 -D HAVE_SYSVSEM_SERIALIZED_ACCEPT
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D HTTPD_ROOT="/home/mfister/vendor/apache-1.3.23"
 -D SUEXEC_BIN="/home/mfister/vendor/apache-1.3.23/sbin/suexec"
 -D DEFAULT_PIDLOG="www/logs/httpd.pid"
 -D DEFAULT_SCOREBOARD="www/logs/httpd.scoreboard"
 -D DEFAULT_LOCKFILE="www/logs/httpd.lock"
 -D DEFAULT_XFERLOG="www/logs/access_log"
 -D DEFAULT_ERRORLOG="www/logs/error_log"
 -D TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"
 -D ACCESS_CONFIG_FILE="conf/access.conf"
 -D RESOURCE_CONFIG_FILE="conf/srm.conf"
Perl:


Summary of my perl5 (revision 5.0 version 6 subversion 1) configuration:
  Platform:
osname=linux, osvers=2.4.13-ac5-20011101-1, archname=i686-linux
uname='linux  2.4.13-ac5-20011101-1 #1 smp thu nov 1 
16:07:19 cst 2001 i686 unknown '
config_args='-des -Doptimize=-g -Dusedevel -Uinstallusrbinperl 
-Ubincompat5005 -Uusemymalloc -Dcc=gcc -pipe -g -I/usr/include/db3 -Dcccdlflags=-fPIC 
-Dinstallprefix=/home/mfister/vendor/perl-5.6.1 
-Dprefix=/home/mfister/vendor/perl-5.6.1 [EMAIL PROTECTED] 
-Dinstallman1dir=/home/mfister/vendor/perl-5.6.1/man/man1 
-Dinstallman3dir=/home/mfister/vendor/perl-5.6.1/man/man3 
-Dman1dir=/home/mfister/vendor/perl-5.6.1/man/man1 
-Dman3dir=/home/mfister/vendor/perl-5.6.1/man/man3 -Dd_dosuid=n -Dd_semctl_semun 
-Di_db -Di_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Uuselargefiles'
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 -pipe -g -I/usr/include/db3', ccflags ='-DDEBUGGING 
-fno-strict-aliasing -I/usr/local/include',
optimize='-g',
cppflags='-DDEBUGGING -fno-strict-aliasing -I/usr/local/include'
ccversion='', gccversion='2.96 2731 (Red Hat Linux 7.1 2.96-85)', 
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 -pipe -g -I/usr/include/db3', 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: DEBUGGING
  Built under linux
  Compiled at Feb  4 2002 13:40:29
  @INC:
/home/mfister/vendor/perl-5.6.1/lib/5.6.1/i686-linux
/home/mfister/vendor/perl-5.6.1/lib/5.6.1
/home/mfister/vendor/perl-5.6.1/lib/site_perl/5.6.1/i686-linux
/home/mfister/vendor/perl-5.6.1/lib/site_perl/5.6.1
/home/mfister/vendor/perl-5.6.1/lib/site_perl
mod_perl:

version:1.26
built with: perl Makefile.PL USE_APXS=1 \
WITH_APXS=/home/mfister/vendor/apache-1.3.23/sbin/apxs \
EVERYTHING=1 CCFLAGS='-pipe -fPIC'
Modules:
---

*** fairly long list *** Will send if necessary ***

Debug Info:
==

Stack Trace:
===
#0  __pthread_mutex_lock (mutex=0x8bf04999) at mutex.c:99
#1  0x401b9cc8 in __libc_free (mem=0x4046cc18) at malloc.c:3152
#2  0x403ce028 in Perl_safesysfree (where=0x4046cc18) at util.c:158
#3  0x403f20d8 in 

Re: Make test issue with the URI module

[dan]

I've read through the previous messages on this topic, and have modified
my blib/lib/Apache/test.pm as did  export PERL_HTTP_URI_CLASS=URI::URL .
Now when I "make test" I get:

Can't locate URI/URL/_generic.pm in @INC (@INC contains: . ../blib/lib
../blib/arch /usr/lib/perl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0
/usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0
/usr/lib/perl5/site_perl ../.) at
/usr/lib/perl5/site_perl/5.6.0/URI/URL.pm line 113.
make: *** [run_tests] Error 2

Any clues? Is my URI::URL screwed up, or do I have problems elsewhere?

Re: [Straying from the Topic] Installing from scratch Apache + mod_perl + Apache::ASP (+maybe others) on unix

[Will Waggoner]

I agree that Apache Toolbox does a nice job for apache/mod_perl
installation -- even goes out and gets the source for you.  I would like to
mention that I got a great deal of benefit from the INSTALL document from
the mod_ssl distribution -- it contains many examples of configuring and
compiling common Apache configurations such as
Apache+SSL+mod_perl+PHP...etc...  It went a long way towards alleviating my
confusion when I first started working with Apache.

Will
- Original Message -
From: "Paul Lindner" <[EMAIL PROTECTED]>
To: "Ged Haywood" <[EMAIL PROTECTED]>
Cc: "Rod Butcher" <[EMAIL PROTECTED]>; "mod_perl Mailing List"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, February 06, 2002 4:09 PM
Subject: Re: [Straying from the Topic] Installing from scratch Apache +
mod_perl + Apache::ASP (+maybe others) on unix


> Two things,
>
> First check out http://www.apachetoolbox.com/ About as out-of-the-box
> as you can get.  Last time I tried it seemed to 'do the right thing'
> for me.
>
> For mod_perl specifics you might also check out chapter 1 of the
> "mod_perl Developer's Cookbook".  I think it's a pretty good stab at
> showing a novice how to compile and install apache+mod_perl (though
> not mod_ssl... alas) The complete chapter is online at
> http://www.modperlcookbook.org/
>
>
> Regards,
> Paul
>
>
> On Thu, Feb 07, 2002 at 12:04:19AM +, Ged Haywood wrote:
> > Hi there,
> >
> > On Thu, 7 Feb 2002, Rod Butcher wrote:
> >
> >
> > > professionals are being driven mad, despite reading the Guide (which
despite
> > > being complete is still mysterious, it comes across as having a
mission
> > > statement to contain everything rather than to be useful, sorry).
> >
> > Patches, chapters, help are always welcome I'm sure.
> >
> > > My .05 is that all development be stopped until the instal process
> > > is up to the same standard as M$. This is what made M$ rich, the
> > > sheer installability and usability. I was visiting somebody
> > > yesterday and he had Win2K installing while we talked for an hour.
> >
> > Yeah, I had a car like that once, but I got rid of it.
> >
> > When I installed the operating system on a Mac last year it took
> > about three minutes - including all the tools, browsers and wotnot
> > that you could wish for - with no intervention from me at all.
> > After the pain I've been through with some W1nd0ze installations
> > it was very refreshing.  So I guess what I'm saying is that there's
> > a lot more to it than that, or Apple would be ruling the world.
> >
> > 73,
> > Ged.
>
> --
> Paul Lindner[EMAIL PROTECTED]   | | | | |  |  |  |   |   |
>
> mod_perl Developer's Cookbook   http://www.modperlcookbook.org/
>  Human Rights Declaration   http://www.unhchr.ch/udhr/index.htm
>

Re: [Straying from the Topic] Installing from scratch Apache + mod_perl + Apache::ASP (+maybe others) on unix

[Paul Lindner]

Two things,

First check out http://www.apachetoolbox.com/ About as out-of-the-box
as you can get.  Last time I tried it seemed to 'do the right thing'
for me.

For mod_perl specifics you might also check out chapter 1 of the
"mod_perl Developer's Cookbook".  I think it's a pretty good stab at
showing a novice how to compile and install apache+mod_perl (though
not mod_ssl... alas) The complete chapter is online at
http://www.modperlcookbook.org/


Regards,
Paul


On Thu, Feb 07, 2002 at 12:04:19AM +, Ged Haywood wrote:
> Hi there,
> 
> On Thu, 7 Feb 2002, Rod Butcher wrote:
> 
> 
> > professionals are being driven mad, despite reading the Guide (which despite
> > being complete is still mysterious, it comes across as having a mission
> > statement to contain everything rather than to be useful, sorry). 
> 
> Patches, chapters, help are always welcome I'm sure.
> 
> > My .05 is that all development be stopped until the instal process
> > is up to the same standard as M$. This is what made M$ rich, the
> > sheer installability and usability. I was visiting somebody
> > yesterday and he had Win2K installing while we talked for an hour.
> 
> Yeah, I had a car like that once, but I got rid of it.
> 
> When I installed the operating system on a Mac last year it took
> about three minutes - including all the tools, browsers and wotnot
> that you could wish for - with no intervention from me at all.
> After the pain I've been through with some W1nd0ze installations
> it was very refreshing.  So I guess what I'm saying is that there's
> a lot more to it than that, or Apple would be ruling the world.
> 
> 73,
> Ged.

-- 
Paul Lindner[EMAIL PROTECTED]   | | | | |  |  |  |   |   |

mod_perl Developer's Cookbook   http://www.modperlcookbook.org/
 Human Rights Declaration   http://www.unhchr.ch/udhr/index.htm

Re: [Straying from the Topic] Installing from scratch Apache +mod_perl + Apache::ASP (+maybe others) on unix

[Ged Haywood]

Hi there,

On Thu, 7 Feb 2002, Rod Butcher wrote:


> professionals are being driven mad, despite reading the Guide (which despite
> being complete is still mysterious, it comes across as having a mission
> statement to contain everything rather than to be useful, sorry). 

Patches, chapters, help are always welcome I'm sure.

> My .05 is that all development be stopped until the instal process
> is up to the same standard as M$. This is what made M$ rich, the
> sheer installability and usability. I was visiting somebody
> yesterday and he had Win2K installing while we talked for an hour.

Yeah, I had a car like that once, but I got rid of it.

When I installed the operating system on a Mac last year it took
about three minutes - including all the tools, browsers and wotnot
that you could wish for - with no intervention from me at all.
After the pain I've been through with some W1nd0ze installations
it was very refreshing.  So I guess what I'm saying is that there's
a lot more to it than that, or Apple would be ruling the world.

73,
Ged.

RE: [?] Same Named Modules, Different Paths

[Stathy G. Touloumis]

Yeah, this is an ideal way to go.  Althought, depending to what degree you
can trust your developers (contractors, etc.) and how much your sys admins
want to admin it may or may not be a good fit.

> > We have a similar issue here but it is designed more for development of
> > modules/code by multiple developers.
>
> If each of your developers runs her own copy of Apache, each copy
> listening to a different port, you can make the namespace collision
> problems go away.  Use a common httpd.conf for all developers with a
> small section specifically for each one, and start Apache separately
> for each developer with '-Ddeveloperid'.  You can trade off between
> the isolation of multiple copies of the complete site(s) on the one
> machine, and the fun of sharing some of the code/data.  I'd keep it
> all separate, discs are cheap enough.
>
> 
>   User ged
>   Port 8011
>   ErrorLog /home/ged/apache/error_log
>   PidFile /tmp/ged.pid
>   LockFile /tmp/...
>   DocumentRoot ...
> 
>
> 
>   User stas
>   Port 8012
>   ErrorLog /home/stas/apache/error_log
>   PidFile /tmp/stas.pid
>   LockFile /tmp/...
>   DocumentRoot ...
> 

Re: Installing from scratch Apache + mod_perl + Apache::ASP (+maybe others) on unix

[Rod Butcher]

This is exactly what I was alluding to in my previous post, and even
professionals are being driven mad, despite reading the Guide (which despite
being complete is still mysterious, it comes across as having a mission
statement to contain everything rather than to be useful, sorry). My .05 is
that all development be stopped until the instal process is up to the same
standard as M$. This is what made M$ rich, the sheer installability and
usability. I was visiting somebody yesterday and he had Win2K installing
while we talked for an hour.
Its no good complaining about the stupidity or laziness of M$ addicts, the
fact that HTML and Javascript jockies are deluded enough to think they can
contemplate installing servers. The fact is they do. And with M$ they CAN.
And that is why corporations will continue to buy M$, rather than get bogged
down in Harry Potter mystic rituals installing free software.
Sorry, this is not meant to criticize anybody (certainly not Joshua,
installing ASP was the least problem), everybody's tried really hard. I'm
available to help if I can, if you need an unsophisticated pro to test
stuff. But please, we need a professional approach to this issue now or
somebody else other than M$ will do it.
regards, Rod
- Original Message -
From: "timj_moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 07, 2002 4:01 AM
Subject: Installing from scratch Apache + mod_perl + Apache::ASP (+maybe
others) on unix

>Okay, I'm having a nightmare trying to install all this on both
>Solaris and AIX. I'm finding the different installation methods for
>each very confusing (and not only that but documentation and posts on
>newsgroups all seem to vary in install methods).

snip snip

>Does anyone have a very simple set of instructions (an 'idiots
>guide', especially aimed at someone who's more of a Windows/IIS
>expert than unix/apache) for installing Apache + mod_perl +
>Apache::ASP that will work every time, including what I need to check
>for on my system (the right permissions, though I'm running as root
>to install, environment variables, required components and files,
>should I be using gcc or not, etc).

RE: [?] Same Named Modules, Different Paths

[Ged Haywood]

Hi all,

On Wed, 6 Feb 2002, Stathy G. Touloumis wrote:

> We have a similar issue here but it is designed more for development of
> modules/code by multiple developers.

If each of your developers runs her own copy of Apache, each copy
listening to a different port, you can make the namespace collision
problems go away.  Use a common httpd.conf for all developers with a
small section specifically for each one, and start Apache separately
for each developer with '-Ddeveloperid'.  You can trade off between
the isolation of multiple copies of the complete site(s) on the one
machine, and the fun of sharing some of the code/data.  I'd keep it
all separate, discs are cheap enough.


  User ged
  Port 8011
  ErrorLog /home/ged/apache/error_log
  PidFile /tmp/ged.pid
  LockFile /tmp/...
  DocumentRoot ...



  User stas
  Port 8012
  ErrorLog /home/stas/apache/error_log
  PidFile /tmp/stas.pid
  LockFile /tmp/...
  DocumentRoot ...



73,
Ged.

Re: Is 'PerlHandler Apache::Registry MySimplePerlModule' possible?

[Cees Hek]

On Thu, 2002-02-07 at 05:31, Zsolt Czinkos wrote:
> Hello 
> 
> Is it possible to insert my Set-Cookie headers after a modperl script?
> for exapmle:
> 
> 
> ...
> PerlFreshRestart On
> PerlModule SetMyCookies
> PerlFixupHandler SetMyCookies
> 
> PerlSetVar SessionDataPath /tmp/apache_session
> PerlSetVar SessionLockPath /tmp/apache_session_lock
> 
> Alias /modperl /home/czinkos/IMI/apache/modperl
> 
> PerlModule Apache::Registry
> SetHandler perl-script
> PerlHandler Apache::Registry SetMyCookies
> Options ExecCGI
> 
> ...
> 
> 
> The script is simple. It adds to cookies to the header.
> e.g. $cookie->bake; 
> 
> I've tried it, but id didn't work. I'd like to add some extra header after 
>everything is done.

You should look at the Apache::Filter module which will allow you to do
this.

Cees

RE: [OT] Server error log says "Accept mutex: sysvsem"

[Kyle Oppenheim]

> However, the sample configuration file supplied with Apache contains no
> AcceptMutex runtime directive nor did I come across documentation
> suggesting how it should be used or where I would learn the options for
> my system (linux, i686, kernel 2.4.7-10).

There's a good description of what the accept mutex is used for on the
Apache Performance Notes page at
http://httpd.apache.org/docs/misc/perf-tuning.html (search down for "accept
Serialization").

Essentially, the call to accept() needs to be serialized to support servers
that listen on multiple ports.  Also, serialization is a performance
optimization on servers that only listen on one port.  I assume that apaci
and/or configure made a good guess for your system when you compiled Apache,
but you can experiment with other methods.  Using a different mutex, if it
works at all, should only help or hurt performance (perhaps using fcntl is
really fast compared to pthreads on your OS).

--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com

Re: Apache::DBI

[clayton cottingham]

"Stathy G. Touloumis" wrote:
> 
> > I'm not sure what you mean, really, but perhaps you mean
> > dbi_connect_method?
> 
> Did you mean specifying this argument like so ?
> 
> DBI->connect( $driver, $u, $p, { dbi_connect_method=> 'connect' } );
> 
> I will see if this is what I am looking for.  Thanks for the reference : )

this is how i usually do it in startup.pl:

#dont declare DBI
use Apache::DBI;

# Initialize the database connections for each child
  Apache::DBI->connect_on_init
  ("DBI:mysql:database=Ezines;host=localhost",
   "root","database",
   {
PrintError => 1, # warn() on errors
RaiseError => 0, # don't die on error
AutoCommit => 1, # commit executes immediately
   }
  );

$Apache::DBI::DEBUG = 1;


then in my code i just use DBI as i normally would:


my $dbh =
  DBI->connect(
   
'dbi:mysql(RaiseError=>1,Taint=>1):dbname=database;host=localhost',
'username', 'password', );

my $count = $dbh->selectrow_array( q{
SELECT
count(*)
FROM
Ezines
},
{},
);


  $dbh->disconnect;




if you tail the log file you should see Apache::DBI::DEBUG messages

Re: Apache::DBI

[Geoffrey Young]

"Stathy G. Touloumis" wrote:
> 
> > I'm not sure what you mean, really, but perhaps you mean
> > dbi_connect_method?
> 
> Did you mean specifying this argument like so ?
> 
> DBI->connect( $driver, $u, $p, { dbi_connect_method=> 'connect' } );

yes, you never call Apache::DBI->connect() directly.

> 
> I will see if this is what I am looking for. 

from what you described in your previous email, I would think it is.

> Thanks for the reference : )

sure :)

--Geoff

[DIGEST] mod_perl digest 2002/01/27

[jgsmith]

--

  mod_perl digest
 
 January 27, 2002 - February 2, 2002

--

Recent happenings in the mod_perl world...


Features

  o mod_perl status
  o module announcements
  o module RFCs
  o available mod_perlers
  o mailing list highlights
  o links


mod_perl status

  o mod_perl
- stable: 1.26 (released July 11, 2001) [1]
- development: 1.26_01-dev [2]
  o Apache
- stable: 1.3.23 (released January 24, 2002) [3]
- development: 1.3.21-dev [4]
  o mod_perl 2.0
- in development (cvs only) [?]
  o Apache 2.0
- beta: 2.0.28 (released November 13, 2001) [5]
  o Perl
- stable: 5.6.1 (released April 9, 2001) [6]
- development: 5.7.2 [7]


module announcements

  o HTML::Template 2.5 - provides HTML templates [8]

  o HTTP::TestEngine 0.02 - HTTP session recorder for later testing
[9]


module RFCs

  o Apache::HEADRegistry - a HEAD request aware version of
Apache::Registry [10]


available mod_perlers

  o experienced Mason looking for a job in Minneapolis [11]


mailing list highlights

  o mod_perl Cookbook and where to buy it [12]

  o Windows mail readers and GPG/PGP [13]

  o mod_perl growth [14]

links

  o The Apache/Perl Integration Project [15]
  o mod_perl documentation [16]
  o mod_perl modules on CPAN [17]
  o mod_perl homepage [18]
  o mod_perl news and advocacy [19]
  o mod_perl list archives
  - modperl@ [20] [21] 
  - dev@ [22] [23]
  - advocacy@ [24]


happy mod_perling...

--James
[EMAIL PROTECTED]

--
[1] http://perl.apache.org/dist/
[2] http://perl.apache.org/from-cvs/modperl/
[3] http://www.apache.org/dist/httpd/
[4] http://dev.apache.org/from-cvs/apache-1.3/
[5] http://www.apache.org/dist/httpd/
[6] http://www.cpan.org/src/stable.tar.gz
[7] http://www.cpan.org/src/devel.tar.gz 

[8] http://mathforum.org/epigone/modperl/thehlaychix
[9] http://mathforum.org/epigone/modperl/blerwelddimp

[10] http://mathforum.org/epigone/modperl/starfaxbi

[11] http://mathforum.org/epigone/modperl/ranswaxtwimp

[12] http://mathforum.org/epigone/modperl/shorfreeyang
[13] http://mathforum.org/epigone/modperl/whimclemkre
[14] http://mathforum.org/epigone/modperl/froxkrungdwun

[15] http://perl.apache.org
[16] http://perl.apache.org/#docs
[17] http://www.cpan.org/modules/by-module/Apache/
[18] http://www.modperl.com
[19] http://www.take23.org
[20] http://mathforum.org/epigone/modperl/
[21] http://marc.theaimsgroup.com/?l=apache-modperl&r=1&w=2
[22] http://marc.theaimsgroup.com/?l=apache-modperl-dev&r=1&w=2
[23] http://www.mail-archive.com/dev%40perl.apache.org/
[24] http://www.mail-archive.com/advocacy@perl.apache.org/

RE: Apache::DBI

[Stathy G. Touloumis]

> I'm not sure what you mean, really, but perhaps you mean
> dbi_connect_method?

Did you mean specifying this argument like so ?

DBI->connect( $driver, $u, $p, { dbi_connect_method=> 'connect' } );

I will see if this is what I am looking for.  Thanks for the reference : )

RE: Apache::DBI

[Stathy G. Touloumis]

> dbi_connect_method?
>
> from man DBI:
>
> The "dbi_connect_method" attribute can be used to specify which driver
> method should be called to establish
> the connection. The only useful values are 'connect',
> 'connect_cached', or some specialized case like
> 'Apache::DBI::connect' (which is automatically the default when
> running within Apache).
>
> so, basically you can create a connection under Apache::DBI that is
> _not_ cached using 'connect'.

Is that using DBI->connect or Apache::DBI->connect . . .

My understanding is that using Apache::DBI pretty much overrides the
functionality of DBI->connect and returns an existing database handle if it
exists (based on parameters passed to method).

I want to be able to return a cached database handle from a method unless a
certain argument is passed.  If this argument is present I would like to
return an independent database handle for perhaps performing transactions.

Re: Apache::DBI

[Geoffrey Young]

"Stathy G. Touloumis" wrote:
> 
> I thought I saw a posting on how to retrieve an independent database handle
> from Apache::DBI  using a certain method call (instead of from the shared
> $dbh for the child).  Does anyone know where this documentation may reside
> (If it is possible).

I'm not sure what you mean, really, but perhaps you mean
dbi_connect_method?

from man DBI:

The "dbi_connect_method" attribute can be used to specify which driver
method should be called to establish
the connection. The only useful values are 'connect',
'connect_cached', or some specialized case like
'Apache::DBI::connect' (which is automatically the default when
running within Apache).

so, basically you can create a connection under Apache::DBI that is
_not_ cached using 'connect'.

is that what you meant?

--Geoff

Apache::DBI

[Stathy G. Touloumis]

I thought I saw a posting on how to retrieve an independent database handle
from Apache::DBI  using a certain method call (instead of from the shared
$dbh for the child).  Does anyone know where this documentation may reside
(If it is possible).


Thanks,

RE: mod_perl "version" for Tomcat

[brian moseley]

On Wed, 6 Feb 2002, Stathy G. Touloumis wrote:

> Hmmm, from what I've read of Tomcat it is recommended to
> use it in conjuction with apache and just proxy specific
> requests to Tomcat.

that's why i recommended he spend his time getting apache
working with ssl.

ps: you don't proxy requests to tomcat, in the http sense;
you delegate request handling to tomcat, passing it info
about the request using the jk or warp protocols.

RE: mod_perl "version" for Tomcat

[Stathy G. Touloumis]

Hmmm, from what I've read of Tomcat it is recommended to use it in
conjuction with apache and just proxy specific requests to Tomcat.

> > Why would you need mod_perl with Tomcat?  You can use
> > Tomcat with Apache using mod_jk, and get the best of
> > both worlds.
>
> presumably so that he doesn't have to port his cgi programs
> to servlets.
>
> i'm pretty sure tomcat has the capability to execute cgi
> programs, but that doesn't buy you the acceleration you get
> with mod_perl.
>
> it's probably worth the original poster's time to figure out
> how to get apache working with ssl so he can continue to use
> mod_perl. his only other realistic choice is using something
> like xml-rpc (or maybe even http) from tomcat to a (non-ssl)
> backend apache/mod_perl.
>

Re: mod_perl "version" for Tomcat

[brian moseley]

On Wed, 6 Feb 2002, Brett W. McCoy wrote:

> Why would you need mod_perl with Tomcat?  You can use
> Tomcat with Apache using mod_jk, and get the best of
> both worlds.

presumably so that he doesn't have to port his cgi programs
to servlets.

i'm pretty sure tomcat has the capability to execute cgi
programs, but that doesn't buy you the acceleration you get
with mod_perl.

it's probably worth the original poster's time to figure out
how to get apache working with ssl so he can continue to use
mod_perl. his only other realistic choice is using something
like xml-rpc (or maybe even http) from tomcat to a (non-ssl)
backend apache/mod_perl.

Re: mod_perl "version" for Tomcat

[Brett W. McCoy]

On Wed, 6 Feb 2002, Chuck Goehring wrote:

> Is there anyone out there working on a mod_perl "version" for Tomcat?
> We currently have Apache running for mod_perl and Tomcat running for a
> purchased servlet library.  I primarily user mod_perl as a "speedup" for
> cgi programs.  I need ssl capabilities and have had problems trying to
> get it working.  Tomcat has an option for ssl from sun that may not have
> the issues on our platform.

Why would you need mod_perl with Tomcat?  You can use Tomcat with Apache
using mod_jk, and get the best of both worlds.

-- Brett
  http://www.chapelperilous.net/

What's the matter with the world?  Why, there ain't but one thing wrong
with every one of us -- and that's "selfishness."
-- The Best of Will Rogers

mod_perl "version" for Tomcat

[Chuck Goehring]

 
 
Is there anyone out there working on a mod_perl 
"version" for Tomcat?  We currently have Apache running for mod_perl and 
Tomcat running for a purchased servlet library.  I primarily user mod_perl 
as a "speedup" for cgi programs.  I need ssl capabilities and have had 
problems trying to get it working.  Tomcat has an option for ssl from sun 
that may not have the issues on our platform.

RE: [?] Same Named Modules, Different Paths

[Stathy G. Touloumis]

We have a similar issue here but it is designed more for development of
modules/code by multiple developers.  This is managed through virtual hosts
and although we do not have our production server the same as development we
are able to view the production code through the development box.  The
development server is significantly slower due to the need to load/unload
modules dynamically as well as perform cleanup but it is not really
noticeable.  Typically there is not a need to work on many modules per
developer change so dynamic loading does not occur often.  We have also
incorporated Mason and template-toolkit into the same architecture
(development/production paths).  Our team is not large nor do we expect it
to grow much (<10) so this may not be applicable for some environments.

I am not sure how your handlers are setup to be executed but for us we have
handlers which can be dynamically called depending on the environment that
you are in (dev,stage,prod).  For development this specific handler can
check if there is a module being developed for that virtual host (developer
change) and take appropriate action (prepend specific path to @INC, cleanup
symbol table/ %INC, load new module) and a cleanup handler which checks to
see if a module was loaded and if so perform cleanup (unload, @INC back,
clean symbol table/%INC and reload non-developer module version).

If you are mostly interested in loading modules specific to the environment
it may be easier to have them on seperate boxes but I think it would be wise
to be sure and manage the code through CVS or some other change management
system as well.

Things are working out well so far : )

> I have a problem, and I have a poor solution; I would like to see if I
> can do even better. My problem is that I have a set of scripts and
> modules that are duplicated on the same Apache server setup. One tree is
> for debugging and developing, the other is the main release site. These
> are managed through cvs. The issue I ran into was that the debug scripts
> would request debug modules, but get the same-named release module if it
> was already loaded in the same Apache process (and vice versa).
>
> Here what my old (buggy under mod_perl) include stuff was like:
>
> use lib "../lib";
> use MyModule;
>
> Here is what I had to do to force correct module loading (mostly stolen
> from the great mod_perl guide):
>
> %INC = (); # Possibly unnecessary
> do 'FindBin.pm';
> unshift @INC, "$FindBin::Bin"; # There are also modules in the same dir
> as the script
> unshift @INC, "$FindBin::Bin/../lib/";
>
> require MyModule;
> import MyModule;
>
>
> So I'm loosing all of that slick compile-time speed savings and clean
> code just so I can have two source trees on the same server. One obvious
> answer is to move the devel tree off of the same server as the release
> tree. I will eventually do that, but it would be cool to see a solution
> that works with my current setup. Is there maybe a way to do tricks to
> modules like Apache::Registry does to scripts by automagically
> prepending the directory name behind the scenes? Any other ideas or
> places to RTFM?
>
> Thanks,
>
> John Heitmann
>
>

Is 'PerlHandler Apache::Registry MySimplePerlModule' possible?

[Zsolt Czinkos]

Hello 

Is it possible to insert my Set-Cookie headers after a modperl script?
for exapmle:


...
PerlFreshRestart On
PerlModule SetMyCookies
PerlFixupHandler SetMyCookies

PerlSetVar SessionDataPath /tmp/apache_session
PerlSetVar SessionLockPath /tmp/apache_session_lock

Alias /modperl /home/czinkos/IMI/apache/modperl

PerlModule Apache::Registry
SetHandler perl-script
PerlHandler Apache::Registry SetMyCookies
Options ExecCGI

...


The script is simple. It adds to cookies to the header.
e.g. $cookie->bake; 

I've tried it, but id didn't work. I'd like to add some extra header after everything 
is done.

thanks in advance

czinkos

Re: [OT] Server error log says "Accept mutex: sysvsem"

[Joerg Plate]

>> The following message keeps appearing in my server error log

>> guess would be that it's harmless.

> Presumably this only happens when you restart the server?

The source file is 'main/http_main.c' and the function is "standalone_main".

 ap_log_error(APLOG_MARK, APLOG_NOERRNO|APLOG_NOTICE,
   server_conf, "Accept mutex: %s (Default: %s)", amutex->name,
   ap_default_mutex_method());

It's just a normal informative message, no need to worry.

> Any apache gurus on this list?
not really...

-- 
"I'm working on it."  

Re: QUESTION

[Tim Tompkins]

if ($redirect = $shortnames->get($fname, WAIT, 1)) {
   if ($redirect !~ /$r->server()->server_hostname/) {
  $r->content_type('text/html');
  $r->header_out ( Location => $redirect ); $log->debug($redirect);

$r->send_http_header;

  return REDIRECT;
 }


Regards,

Tim Tompkins
--
Programmer
http://www.arttoday.com/
http://www.rebelartist.com/
--
- Original Message -
From: Martin Haase-Thomas
To: [EMAIL PROTECTED]
Sent: Wednesday, February 06, 2002 8:21 AM
Subject: QUESTION


Hi all,

I hope there'll be someone here to help we with a mod_perl prob, of
which I thought first it wouldn't be one. I refer to the "Writing Apache
Modules" book by Stein/MacEachern.

The prob is quite simple: I have to redirect certain requests under
certain conditions to another URL (and please believe me: I tried with
mod_rewrite, this way seems to be more efficient). I'm using Apache
1.3.22 on Debian Linux 2.4.17.

These are the lines from my httpd.conf:

PerlFreshRestart On
PerlTaintCheck On
PerlSetEnv SHORTNAMES /etc/apache/shortnames.txt
PerlAddVar PROJECT_DOCUMENT_ROOT /home/disp05/app/fn/
PerlRequire /usr/local/sbin/appstart


   SetHandler perl-script
   PerlHandler Apache::StaticServer


The stanza in StaticServer.pm that fails is:

 if ($redirect = $shortnames->get($fname, WAIT, 1)) {
   if ($redirect !~ /$r->server()->server_hostname/) {
  $r->content_type('text/html');
  $r->header_out ( Location => $redirect ); $log->debug($redirect);
  return REDIRECT;
   }
 ...
 }

$shortnames is an Apache::SharedMem segment, containing a vast amount of
shortnames as keys and the corresponding URLs as values. The funny thing
is now, that although I do everything exactly as I find it in the book
on p.125 (content_type, header_out, REDIRECT), I get pure nonsense.

This is what a libwww-perl client displays when I try to access the address:
500 (Internal Server Error) unexpected EOF before status line seen
Client-Date: Wed, 06 Feb 2002 13:40:25 GMT

This is what I find in access_log:
192.168.255.75 - - [06/Feb/2002:14:46:24 +0100] "GET /psycho HTTP/1.0"
200 - "-" "libwww-perl/5.50"

And this is what stands in error_log:
[Wed Feb  6 14:46:24 2002] [debug]
/usr/local/share/perl/5.6.1/Apache/StaticServer.pm(45): [client
192.168.255.75] http://www.domain.de/app/fn/portal_welcome_jsp/52329.html

The error log proves that the second if() matches, as the entry comes
from my $log->debug(...).

Has anyone got an idea? I'm close to depression -;)

Many thanx in advance
Martin

QUESTION

[Martin Haase-Thomas]

Hi all, 

I hope there'll be someone here to help we with a mod_perl prob, of 
which I thought first it wouldn't be one. I refer to the "Writing Apache 
Modules" book by Stein/MacEachern. 

The prob is quite simple: I have to redirect certain requests under 
certain conditions to another URL (and please believe me: I tried with 
mod_rewrite, this way seems to be more efficient). I'm using Apache 
1.3.22 on Debian Linux 2.4.17. 

These are the lines from my httpd.conf: 

    PerlFreshRestart On 
    PerlTaintCheck On 
    PerlSetEnv SHORTNAMES /etc/apache/shortnames.txt 
    PerlAddVar PROJECT_DOCUMENT_ROOT 
/home/disp05/app/fn/
    PerlRequire /usr/local/sbin/appstart 

     
   SetHandler perl-script 
   PerlHandler Apache::StaticServer 
     

The stanza in StaticServer.pm that fails is: 

 if ($redirect = $shortnames->get($fname, WAIT, 1)) { 
   if ($redirect !~ /$r->server()->server_hostname/) { 
  $r->content_type('text/html'); 
  $r->header_out ( Location => $redirect ); $log->debug($redirect); 

  return REDIRECT; 
   } 
 ... 
 } 

$shortnames is an Apache::SharedMem segment, containing a vast amount of 
shortnames as keys and the corresponding URLs as values. The funny thing 
is now, that although I do everything exactly as I find it in the book 
on p.125 (content_type, header_out, REDIRECT), I get pure nonsense. 

This is what a libwww-perl client displays when I try to access the address: 

500 (Internal Server Error) unexpected EOF before status line seen 
Client-Date: Wed, 06 Feb 2002 13:40:25 GMT 

This is what I find in access_log: 
192.168.255.75 - - [06/Feb/2002:14:46:24 +0100] "GET /psycho HTTP/1.0" 
200 - "-" "libwww-perl/5.50" 

And this is what stands in error_log: 
[Wed Feb  6 14:46:24 2002] [debug] 
/usr/local/share/perl/5.6.1/Apache/StaticServer.pm(45): [client 
192.168.255.75] 
http://www.domain.de/app/fn/portal_welcome_jsp/52329.html

The error log proves that the second if() matches, as the entry comes 
from my $log->debug(...). 

Has anyone got an idea? I'm close to depression -;) 

Many thanx in advance 
Martin 

Re: image corruption

[Tim Noll]

First of all, let me apologize for the hacked-up code I sent with my
original post. I was actually trying to return my current code back to
something that looked more like the TT sample code, but I clearly didn't
do a very good job. (In my actual code, I've moved
$r->send_http_header() until after the $template->process() call so that
I can trap file not found errors.)

In any case, thanks to David Ranney. Adding this to my config file does
the trick:

Alias /tt/images /usr/local/apache/tt/html/images

SetHandler default-handler


Thanks.

-Tim


- Original Message -
From: "Lyle Brooks" <[EMAIL PROTECTED]>
To: "Tim Noll" <[EMAIL PROTECTED]>
Cc: "Lyle Brooks" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, February 05, 2002 5:54 PM
Subject: Re: image corruption


>
> Ok, a couple of things...
>
> 1) You want to move the $r->send_http_header; call up before calling
>$template->process();
>
> 2) Modify $template->process( $file, $vars, $r) to
>   $template->process( $file, $vars) since you specify OUTPUT
=> $r
>when you create the Template object (so it's re-dundant).
>
> 3) get rid of the $r->print( $output ) line as well,
$template->process()
> is going to send the output to Apache the way you have it setup.
>
>
> 4) As David Ranney pointed out in a previous post, you might want to
> put your images somewhere else, or adjust your URL
>
> You get a path_info part only for the virtual component of your URL
> (ie. there's no filesystem component beyond /tt ), but your URL for
> images/hello.gif is relative to /tt, which means your handler for
>  has got to fix things up.
>
> ...or..
>
> If you make the URL hello.gif to resolve to something outside /tt,
> then Apache should serve it up as a regular file, which I suspect is
> what you want.
>
> HTH
>
> Lyle
>
>
>
>
> Quoting Tim Noll ([EMAIL PROTECTED]):
> > Whoops, I hacked up my example a little to make it easier it to
read,
>
> > and I accidentally removed the line:
> > $file =~ s{^/}{};
> > But, it was in the original. Really. :-)
> >
> > -Tim
> >
> >
> > - Original Message -
> > From: "Lyle Brooks" <[EMAIL PROTECTED]>
> > To: "Tim Noll" <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Tuesday, February 05, 2002 4:42 PM
> > Subject: Re: image corruption
> >
> >
> > > When I try this example, I find that this line
> > >
> > > >  my $file = $r->path_info;
> > >
> > > will set $file to "/index.html" when I request the URL
/tt/index.html
> > >
> > > which leads to an error message that says,
> > >
> > > reason: file error - /index.html: absolute paths are not allowed
(set
> > ABSOLUTE option)
> > >
> > > You may want to clip off the leading slash or set the Template
Toolkit
> > > option ABSOLUTE, depending on which suits your needs.
> > >
> > > Quoting Tim Noll ([EMAIL PROTECTED]):
> > > > I'm attempting to use mod_perl and Template Toolkit to serve up
> > > > templates. However, I'm having a problem with the images in
those
> > > > templates: They're passing through the content handler, and thus
> > getting
> > > > corrupted.
> > > >
> > > > My first thought was to return DECLINED from the content handler
if
> > the
> > > > request is not for text/html content; however, since I'm using a
> > > > Location directive, the content_type is always empty since
there's
> > no
> > > > direct mapping to an actual image file. I could use an Alias to
map
> > the
> > > > URI to the file, but then I wouldn't have the path_info that I'm
> > using
> > > > to call the template.
> > > >
> > > > Since my test code, using path_info, is based on an example from
the
> > > > Template Toolkit docs, I feel like I'm probably overlooking
> > something
> > > > basic. So, I'd appreciate it if someone could show me the error
of
> > my
> > > > ways. :-)
> > > >
> > > > Here are the relevant chunks of config and code:
> > > >
> > > > from httpd.conf
> > > > ---
> > > > ...
> > > > 
> > > >  SetHandler perl-script
> > > >  PerlHandler Apache::Test::Mod
> > > >  PerlSetVar WEBROOT /usr/local/apache/tt/html
> > > > 
> > > > ...
> > > >
> > > > Apache::Test::Mod
> > > > -
> > > > ...
> > > > sub handler {
> > > >  my $r = shift;
> > > >
> > > >  # this doesn't work
> > > >  #return DECLINED unless $r->content_type eq 'text/html';
> > > >
> > > >  my $WEBROOT = $r->dir_config('WEBROOT')
> > > >   or return fail( $r, SERVER_ERROR, "'WEBROOT' not specified" );
> > > >
> > > >  my $file = $r->path_info;
> > > >
> > > >  my $vars = {
> > > >   content  => $r->content_type,
> > > >  };
> > > >
> > > >  $r->content_type('text/html');
> > > >  $r->no_cache(1);
> > > >
> > > >  my $template = Template->new( {
> > > >   INCLUDE_PATH => "$WEBROOT:$WEBROOT/include",
> > > >   OUTPUT   => $r,
> > > >  } );
> > > >  $template->process( $file, $vars, $r)
> > > >   or return fail( $r, SERVER_ERROR, $template->error );
> > > >
> > > >  $r->send_http_header();
> > > >  $r->print( $output );
> > > >
> > > >  return OK;
> > > > }
> > >

RE: [OT] Server error log says "Accept mutex: sysvsem"

[Al Pacifico]

Ged-
You are correct; a little more delving suggests that it has to do with
Apache, but not mod_perl. The message appears only when the server is
started.

Apache was compiled from the mod_perl source tree using only the
following options:
APACHE_SRC=../usr/apache...
APACHE_PREFIX=/usr/local/apache
EVERYTHING=1
DO_HTTPD=1
USE_APACI=1

httpd -l produces the following output:
Compiled-in modules:
  http_core.c
  mod_env.c
  mod_log_config.c
  mod_mime.c
  mod_negotiation.c
  mod_status.c
  mod_include.c
  mod_autoindex.c
  mod_dir.c
  mod_cgi.c
  mod_asis.c
  mod_imap.c
  mod_actions.c
  mod_userdir.c
  mod_alias.c
  mod_access.c
  mod_auth.c
  mod_setenvif.c
  mod_perl.c
suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec

A Google groups search on 'accept mutex' yields plenty of posts
reporting this message, but most of them involve apache not starting and
other configuration/permissions errors.

The changes file (since 1.3.22) mentions the following:

  *) Addition of the AcceptMutex runtime directive. The accept mutex
 method is now runtime controllable. The suite of available methods
 per platform is defined at compile time (with
HAVE_FOO_SERIALIZED_ACCEPT
 noting that the method is available and works, and
 USE_FOO_SERIALIZED_ACCEPT noting that it should be the default
 method in absense of any AcceptMutex line, or via AcceptMutex
default)
 and selectable at runtime. The full (current) suite is uslock,
 pthread, sysvsem, fcntl, flock, os2sem, tpfcore and none, but
 not all platforms accept all methods. [Jim Jagielski]

However, the sample configuration file supplied with Apache contains no
AcceptMutex runtime directive nor did I come across documentation
suggesting how it should be used or where I would learn the options for
my system (linux, i686, kernel 2.4.7-10).

Any apache gurus on this list?

-al
Al Pacifico
Seattle, WA

-Original Message-
From: Ged Haywood [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 06, 2002 4:55 AM
To: Rafiq Ismail (ADMIN)
Cc: Al Pacifico; [EMAIL PROTECTED]
Subject: Re: [OT] Server error log says "Accept mutex: sysvsem"

Hi there,

On Wed, 6 Feb 2002, Rafiq Ismail (ADMIN) wrote:

> > The following message keeps appearing in my server error log
> guess would be that it's harmless.

Nothing to do with mod_perl, check the Apache docs (performance tuning
guide).
Presumably this only happens when you restart the server?

73,
Ged.

Re: libapreq problem and mozilla 0.97

[Joe Schaefer]

"Rob Mueller (fastmail)" <[EMAIL PROTECTED]> writes:

> Note the extra blank line, which I think the lack of is causing the
> problem under 0.97.

I'm pretty sure we can come up with a reasonable work-around for 1.0,
but it would really help if you can:

  1) rebuild libapreq with debugging:
  % perl Makefile.PL DEFINE=-DDEBUG
  % make && make install

  2) test it again and submit both the raw upload data
  and your error log to [EMAIL PROTECTED]

Thanks alot.
-- 
Joe Schaefer

Re: [OT] Server error log says "Accept mutex: sysvsem"

[Ged Haywood]

Hi there,

On Wed, 6 Feb 2002, Rafiq Ismail (ADMIN) wrote:

> > The following message keeps appearing in my server error log
> guess would be that it's harmless.

Nothing to do with mod_perl, check the Apache docs (performance tuning guide).
Presumably this only happens when you restart the server?

73,
Ged.

Re: Server error log says "Accept mutex: sysvsem"

[Rafiq Ismail (ADMIN)]

Not sure but it just looks like you're getting confirmation of semaphore
locking which is probably occuring between the different processes - I'd
guess.  Then again, it's worrying that it's being directed to STDERR.  My
guess would be that it's harmless.  Check the options with which you
rebuilt apache; you haven't got excessive debugging info have you?

Someone with much more wisdom may prove me wrong - I'm just filling an
empty moment with speculation. :)
fiq



On Tue, 5 Feb 2002, Al Pacifico wrote:

> The following message keeps appearing in my server error log after
> building a newer version of Apache (v.1.3.23) and mod_perl (v.1.26) than
> I had been running. I never saw this before (I think I had Apache 1.3.20
> with mod_perl 1.24 most recently).
> What does it mean and should I worry?
>
>  [Tue Feb  5 11:44:46 2002] [notice] Accept mutex: sysvsem (Default:
> sysvsem)
>
> Thanks in advance.
> -al
> Al Pacifico
> Seattle, WA
>
>