Re: [OT now] Re: Template techniques
On Fri, 9 Jun 2000, Joshua Chamas wrote: > Perrin Harkins wrote: > > > > On Fri, 9 Jun 2000, Drew Taylor wrote: > > > I really like the fact that templates can be compiled to perl code & > > > cached. Any others besides Mason & EmbPerl (and TT in the near future)? > > > > Sure: Apache::ePerl, Apache::ASP, Text::Template, and about a million > > unreleased modules that people wrote for their own use. (I think writing > > a module that does this should be a rite of passage in Perl hacking.) > > > > For my second rite of passage, I'm hacking XML::XSLT > integration into Apache::ASP for realtime XSLT document > rendering XML::XSLT has an interesting definition of realtime ;-) I seriously suggest you check out Sablotron from www.gingerall.com - it's an amazingly quick XSLT engine with a Perl module. -- Fastnet Software Ltd. High Performance Web Specialists Providing mod_perl, XML, Sybase and Oracle solutions Email for training and consultancy availability. http://sergeant.org http://xml.sergeant.org
Re: [DESPERATE] Problems with apache-php3perl SRPM
On Sat, 10 Jun 2000, you wrote: > I know this is really basic, but you did check to be sure that the > loadmodule/addmodule directives for modperl come before the problem > PerlHandler directive? Otherwise it won't recognize the PerlHandler > directive because modperl will not have been loaded at that time. The addmodule/loadmodule is not needed since i compiled mod_perl.c statically into apache. Note the binary is 2MB++ ! And the loading of mod_actions is _before_ the Perl statements. > > I've also had problem, not with the PerlHandler directive, but with my own > custom directives. I finally downgraded my Apache to 1.3.6 and my problems > went away (in other words, the problem is either Apache or modperl or > possibly in the interface between them). If your running a more recent > version, try downgrading and see what that does. If nothing else, that > will better help folks to figure out where the problem is not. Actually my previous version of apache+mod_perl static _was_ 1.3.6, and that worked even with EmbPerl. Now i want to "up" the versions of all three if i could, and i came across this SRPM. However, it doesn't seem to work. \8( > > -- Rob > > --On 06/10/00 11:54:09 +0800 "Ian C.Sison" <[EMAIL PROTECTED]> wrote: > > > > > On Sat, 10 Jun 2000, you wrote: > >> On Sat, Jun 10, 2000 at 01:04:49AM +0800, Ian C.Sison wrote: > >> > Hi all, > >> > > >> > I've tried working with the apache-php3perl SRPM which was posted on > >> > the > >> > >> snip > >> > >> > Starting httpd: Syntax error on line 862 of /etc/httpd/conf/httpd.conf: > >> > Invalid command 'PerlHandler', perhaps mis-spelled or defined by a > >> > module not included in the server configuration > >> > > >> > Now i know the FAQ entries on this error code, but i know perl is > >> > included and linked statically, so the keyword PerlHandler should > >> > work. Looking at httpd -l I get: > >> > > >> > Compiled-in modules: > >> > http_core.c > >> > mod_so.c > >> > mod_perl.c > >> > mod_php3.c > >> > suexec: enabled; valid wrapper /usr/sbin/suexec > >> > > >> > > >> > >> snip > >> > >> > >> > >> IIRC from the mod_perl docs, mod_action.c is the only one that HAS to be > >> in there for mod_perl... add that and see. > > > > LoadModule action_module modules/mod_actions.so > > AddModule mod_actions.c > > > > I've checked and they are both in my httpd.conf. > > Still no resultion to this. > > > > I tend to believe that this is not a problem due to the fact that i built > > this from an SRPM. I think it's a bug in apache or mod_perl that > > probably hasn't been discovered yet. It's clear from httpd -l that > > mod_perl.c is included, so why does not it recognize the Perl > > configuration phrases/words? > > > > Anyone else with some ideas? > > --- > > > > >_ _ _ _ __ _ _ _ _ > /\_\_\_\_\/\_\ /\_\_\_\_\_\ > /\/_/_/_/_/ /\/_/ \/_/_/_/_/_/ QUIDQUID LATINE DICTUM SIT, > /\/_/__\/_/ __/\/_//\/_/ PROFUNDUM VIDITUR >/\/_/_/_/_/ /\_\ /\/_//\/_/ > /\/_/ \/_/ /\/_/_/\/_//\/_/ (Whatever is said in Latin > \/_/ \/_/ \/_/_/_/_/ \/_/ appears profound) > > Rob Tanner > McMinnville, Oregon > [EMAIL PROTECTED]
[OT - Security] Linux vulnerability
Hi all, I thought this might be of interest to Apache users running Linux. > A vulnerability in some versions of Linux has recently been > identified. > > SYSTEMS AFFECTED > > Linux kernel versions 2.2.x before 2.2.16 > (2.0.x are safe; 2.2.16 is safe) > > IMPACT > > Any local user can gain root privileges << > > TO FIX > > Upgrade to kernel 2.2.16 > > REFERENCES > > Postings regarding the vulnerability to BUGTRAQ: > > > http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-06-01&m > [EMAIL PROTECTED] > > http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-06-01&m > sg=070b01bfd0cd$95b678e0$[EMAIL PROTECTED] > > http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-06-01&m > [EMAIL PROTECTED] > > Source for Linux kernel version 2.2.16: > > http://www.kernel.org/pub/linux/kernel/v2.2/linux-2.2.16.tar.gz > > NOTES > > Don't be confused by the references to Sendmail in the descriptions > of the bug - its role in this vulnerability is incidental and other > setuid programs may be usable in a similar way. > > 73, Ged.
Re: Template techniques [ newbie alert + long ]
Hi there, On Thu, 8 Jun 2000, Perrin Harkins wrote: > use references for passing data. But see "Advanced Perl Programming" pages 9 (Performance Efficiency) and 44 (Using Typeglob Aliases). 73, Ged.
mod_perl not to work with 5.6?
Hey, who of the Perl teachers at Cruise said that? http://www.oreillynet.com/pub/a/network/2000/06/06/geekcruise.html 8.Perl 5.6, which seems like generally a very good thing, currently doesn't work in a mod_perl (i.e., Apache) context. This is a big problem for some people. I guess a correction and an apology are due... :) I know that not everything is slick, but having such a bald claim... _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://perl.org http://stason.org/TULARC http://singlesheaven.com http://perlmonth.com http://sourcegarden.org
RE: [OT now] Re: Template techniques
> > For my second rite of passage, I'm hacking XML::XSLT > integration into Apache::ASP for realtime XSLT document > rendering with a sophisticated caching engine utilizing > Tie::Cache. Moving forward, the XML buzzword seems to be > just about a necessity. > > Take it as a sign of respect Matt :) > And to add one to the list, Embperl 2.0 will also support XML and XSLT :-) Gerald - Gerald Richterecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice:+49 6133 925151 WWW:http://www.ecos.de Fax: +49 6133 925152 -
Re: [OT - Security] Linux vulnerability
On Sat, 10 Jun 2000, Ged Haywood wrote: > Hi all, > > I thought this might be of interest to Apache users running Linux. [snip] Note that this is not a vulnerability that Apache/Linux suffers from particularly, except in the case of a mod_perl or CGI exploit that allows the user to get a local account on the machine, in which case he/she can "upgrade" that account to root using this exploit. Of course you should probably say "to hell with my 90+ days uptime" and upgrade anyway ;-) -- Fastnet Software Ltd. High Performance Web Specialists Providing mod_perl, XML, Sybase and Oracle solutions Email for training and consultancy availability. http://sergeant.org http://xml.sergeant.org
Re: mod_perl not to work with 5.6?
> "Stas" == Stas Bekman <[EMAIL PROTECTED]> writes: Stas> Hey, who of the Perl teachers at Cruise said that? Stas> http://www.oreillynet.com/pub/a/network/2000/06/06/geekcruise.html Stas> Stas> 8.Perl 5.6, which seems like generally a very good thing, currently Stas> doesn't work Stas> in a mod_perl (i.e., Apache) context. This is a big problem for some Stas> people. Stas> Stas> I guess a correction and an apology are due... :) I don't think it was me, unless it was a misquote. From what I understand, Perl 5.6 *threads* don't play well with mod_perl. Is that accurate? But then again, 5.6 threads are semi-fragile anyway. :) And wasn't some part of 5.6 broken with respect to HTML::Mason? (Which of course concerns me greatly. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
Re: [DESPERATE] Problems with apache-php3perl SRPM
omigod...! It worked! Ok now, i've commented out the ClearModuleList directive , apache loaded ok. Would there be any side effects to the directive, as it seemed to be there for a purpose... Thanks for your help! Ian On Sat, 10 Jun 2000, Ged Haywood wrote: > Hi there, > > On Sat, 10 Jun 2000, Ian C.Sison wrote: > > > > > Starting httpd: Syntax error on line 862 of /etc/httpd/conf/httpd.conf: > > > > Invalid command 'PerlHandler', perhaps mis-spelled or defined by a module > > > > not included in the server configuration > > > Anyone else with some ideas? > > Have you got a ClearModuleList directive in your config somewhere? > > 73, > Ged. > > >
RE: [OT now] Re: Template techniques
Has anybody run into any Perl libraries that do XSLT transformations that are usuable? Last I looked, there was no library that implemented the spec or provided a useful API. Maybe I'm behind the times... Today, Gerald Richter <[EMAIL PROTECTED]> frothed and gesticulated about RE:...: > > For my second rite of passage, I'm hacking XML::XSLT > > integration into Apache::ASP for realtime XSLT document > > rendering with a sophisticated caching engine utilizing > > Tie::Cache. Moving forward, the XML buzzword seems to be > > just about a necessity. > > > > Take it as a sign of respect Matt :) > > > > And to add one to the list, Embperl 2.0 will also support XML and XSLT :-) > > Gerald > > > - > Gerald Richterecos electronic communication services gmbh > Internetconnect * Webserver/-design/-datenbanken * Consulting > > Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz > E-Mail: [EMAIL PROTECTED] Voice:+49 6133 925151 > WWW:http://www.ecos.de Fax: +49 6133 925152 > - > > -- Salon Internet http://www.salon.com/ Manager, Software and Systems "Livin' La Vida Unix!" Ian Kallen <[EMAIL PROTECTED]> / AIM: iankallen / Fax: (415) 354-3326
RE: [OT now] Re: Template techniques
On Sat, 10 Jun 2000, Ian Kallen wrote: > > Has anybody run into any Perl libraries that do XSLT transformations that > are usuable? Last I looked, there was no library that implemented the > spec or provided a useful API. Maybe I'm behind the times... Sablotron from http://www.gingerall.com/ - all it lacks is xsl:number, as far as I know. AxKit has full support for XSLT transformations via Sablotron. However perl users interested in server side transformations might also be interested in XPathScript. I have a new guide to XPathScript up at http://xml.sergeant.org/axkit/xpathscript/guide.dkb -- Fastnet Software Ltd. High Performance Web Specialists Providing mod_perl, XML, Sybase and Oracle solutions Email for training and consultancy availability. http://sergeant.org http://xml.sergeant.org
Re: [DESPERATE] Problems with apache-php3perl SRPM
Hi again, On Sat, 10 Jun 2000, Ian C. Sison wrote: > > omigod...! > > It worked! > Ok now, i've commented out the ClearModuleList directive , apache loaded > ok. Would there be any side effects to the directive, as it seemed to be > there for a purpose... Well not side-effects exactly... the most usual reason for this directive is to get rid of a module which has effects that you don't want but which happens to be compiled in. Trouble is then you have to put AddModule/LoadModule directives into the configuration to get back the modules you _do_ want because ClearModuleList, er, Clears Apache's Module List. So you can either recompile Apache with just the modules you want, or (horrors!) use DSO and only pull in the ones you want, or carry on as you are if it works OK as it is. The httpd processes will be a little bigger than necessary if it has modules compiled in that you don't need. No matter. > Thanks for your help! Aw, shucks. 73, Ged.
Re: Big pages and gzip
[EMAIL PROTECTED] (Doug MacEachern) wrote: >On Wed, 7 Jun 2000, Ken Williams wrote: > >> [EMAIL PROTECTED] (Stas Bekman) wrote: >> >> >On Wed, 7 Jun 2000, Mark Hewis wrote: >> > >> >> it would seem to be quite straight forward to implement a handler >> >> to gzip all output html files depending on the allowed mime-types >> >> and/or user_agent. This would reduce many pages by up to a factor >> >> of 10 in size. >> >> >> >> 1) Is anyone already doing? >> >> 2) If not why not? >> >> 3) what borwsers would accept html files in a gzipped format >> > >> >it's there for a long time: >> >Apache::Gzip >> >Apache::GzipChain >> >> Actually, as far as I know there's no Apache::Gzip. > >close, there is an Apache::GZip in the eagle book and code available >modperl.com Darn. Or perhaps: cool. Is it possible for me to usurp this module? The Apache::Gzip module I've been working on has the same goals and same purpose as the one in the eagle, but a bit of a different interface and a very different implementation inside. It's reasonable that if the only thing changing is the interface (can I say that with a straight face?), the module could be kept the same. Doug, what do you think? I assume it would be a bad idea to have two modules, an Apache::GZip (from the book) and an Apache::Gzip (on CPAN). Or might that be okay, if notes were added to the docs for each? -Ken
error message
I recently started to use modperl. Ever since I have been getting the following message in error_log. It repeats itself as long as a browser is requesting a uri being handled by modperl null: Attempt to free unreferenced scalar at /dev/null line <#> chunk # Can someone explain what this means or how should I go about debugging. I have a hunch it might be taint checking, but I don't know. Thank you, Alex Vladimirskiy
Re: $r->register_cleanup limits (Problem Solved)
Doug MacEachern writes:
> there's no limit the number of cleanups you can register, but i would
> still push the sub {}'s into an array and register a single cleanup to
> iterate over them.
you're right that wasn't the problem, I was passing the same
Image::Magick reference to each subroutine, and as it read in pictures
it kept using more and more memory until it ran out of and killed the
process.
I did as you suggested though and now there's only one cleanup,
thanks!
--
[EMAIL PROTECTED]
RE: [OT now] Re: Template techniques
At 17:10 10/06/2000 +0100, Matt Sergeant wrote: >On Sat, 10 Jun 2000, Ian Kallen wrote: > >> >> Has anybody run into any Perl libraries that do XSLT transformations that >> are usuable? Last I looked, there was no library that implemented the >> spec or provided a useful API. Maybe I'm behind the times... > >Sablotron from http://www.gingerall.com/ - all it lacks is xsl:number, as >far as I know. No it actually lacks pretty much more than that. Most things are roughly implemented but the devil is in the details. Controlling output is painful (through xsl:output, disable-output-escaping and friends) and other things don't work exactely as expected, leading to some teeth gnashing. There are also a few bugs in the current release. However it is moving fast and I think that it'll be stable soon enough. The biggest problem imho that might not be solved too soon is that it's string-in string-out, no support for SAX (from the Perl interface). The performance is getting much better too, though I still get better results piping through Saxon (haven't tried this in mod_perl though). -- robin b. Smoking is one of the leading causes of statistics.
FINALE: (or finally!) Re: Can't create custom config directives(long)
And the really GOOD NEWS!!! When I upgraded to mod_perl 1.24, the problem
went away. It all works like it's suppossed to now.
--On 06/09/00 12:02:40 -0700 Doug MacEachern <[EMAIL PROTECTED]> wrote:
> On Thu, 8 Jun 2000, Rob Tanner wrote:
>
>> MirrorWiseKeyFile', perhaps mis-spelled or defined by a module not
>> included in the server configuration
> ...
>> > PerlModule Apache::MirrorWise
>
> this is becoming a common problem, try this bandaid, instead of that
> PerlModule line:
>
>
> delete $INC{'Apache/MirrorWise.pm'};
> require Apache::MirrorWise;
>
>
>
-- Rob
_ _ _ _ __ _ _ _ _
/\_\_\_\_\/\_\ /\_\_\_\_\_\
/\/_/_/_/_/ /\/_/ \/_/_/_/_/_/ QUIDQUID LATINE DICTUM SIT,
/\/_/__\/_/ __/\/_//\/_/ PROFUNDUM VIDITUR
/\/_/_/_/_/ /\_\ /\/_//\/_/
/\/_/ \/_/ /\/_/_/\/_//\/_/ (Whatever is said in Latin
\/_/ \/_/ \/_/_/_/_/ \/_/ appears profound)
Rob Tanner
McMinnville, Oregon
[EMAIL PROTECTED]
Apache::DProf tip
Here's something that might be obvious to others but took me a while to figure out: If you want to get useful profiling information, you need to initialize the debugger before your modules get compiled. If you pull in your modules from startup.pl, you can accomplish this by putting a block like this in your httpd.conf before the "PerlRequire startup.pl" statement: use Apache::DProf; use Apache::DB; Apache::DB->init; The "PerlModule Apache::DProf" directove suggested in the Apache::DProf docs also seems to work, but be careful because load order seems to matter here. - Perrin
