RE: loss of shared memory in parent httpd

2002-03-17 Thread Ged Haywood

Hi all,

On Sat, 16 Mar 2002, Bill Marrs wrote:

 leads ones to wonder if some of our assumptions or tools used to 
 monitor memory are inaccurate or we're misinterpreting them.

Well 'top' on Linux is rubbish for sure.

73,
Ged.




[ANNOUNCE] Apache::FillInForm

2002-03-17 Thread Maurice Aubrey

http://www.creation.com/~maurice/Apache-FillInForm-0.01.tar.gz
I'll put it on CPAN if there's interest.

NAME
Apache::FillInForm - mod_perl interface to HTML::FillInForm

SYNOPSIS
httpd.conf:

  PerlModule Apache::Filter
  PerlModule Apache::FillInForm
  FilesMatch \.foo$
PerlSetVar Filter on
PerlHandler Apache::RegistryFilter Apache::FillInForm
  /FilesMatch

And then somewhere in your application:

  use Apache::FillInForm;
  Apache::FillInForm-fill; # We have a form to fill out

DESCRIPTION
This is a mod_perl filter that uses HTML::FillInForm and Apache::Request
to automatically populate forms with user submitted data.

Your application should call Apache::FillInForm-fill to indicate that
you need a form filled in. If you don't do that, the filter passes the
content through unmodified to minimize the performance hit for pages
with no forms. Regardless of how many times you call
Apache::FillInForm-fill, your content will only be filtered once per
request.

The data source for the forms is taken from Apache::Request by calling
its instance() method. If you're unfamiliar with how the instance()
method works, see the Apache::Request documentation.

If you don't want to use Apache::Request you should be able to subclass
this module and override its data() method. The data() method should
return either a hash reference or an object that has a CGI.pm-style
param() interface.

BUGS
May want to allow specific forms to be targeted by name and use separate
data sources for each.

Warning: This interface is experimental and may change based on
experience and feedback.

AUTHOR
Copyright 2002, Maurice Aubrey [EMAIL PROTECTED]. All rights
reserved.

This module is free software; you may redistribute it and/or modify it
under the same terms as Perl itself.

SEE ALSO
perl(1), mod_perl(3), Apache(3), Apache::Filter(3), HTML::FillInForm(3),
Apache::Request(3)



Re: [ANNOUNCE] Apache::FillInForm

2002-03-17 Thread Mark Maunder

Why not just use HTML::FillInForm?

Maurice Aubrey wrote:

 http://www.creation.com/~maurice/Apache-FillInForm-0.01.tar.gz
 I'll put it on CPAN if there's interest.

 NAME
 Apache::FillInForm - mod_perl interface to HTML::FillInForm

 SYNOPSIS
 httpd.conf:

   PerlModule Apache::Filter
   PerlModule Apache::FillInForm
   FilesMatch \.foo$
 PerlSetVar Filter on
 PerlHandler Apache::RegistryFilter Apache::FillInForm
   /FilesMatch

 And then somewhere in your application:

   use Apache::FillInForm;
   Apache::FillInForm-fill; # We have a form to fill out

 DESCRIPTION
 This is a mod_perl filter that uses HTML::FillInForm and Apache::Request
 to automatically populate forms with user submitted data.

 Your application should call Apache::FillInForm-fill to indicate that
 you need a form filled in. If you don't do that, the filter passes the
 content through unmodified to minimize the performance hit for pages
 with no forms. Regardless of how many times you call
 Apache::FillInForm-fill, your content will only be filtered once per
 request.

 The data source for the forms is taken from Apache::Request by calling
 its instance() method. If you're unfamiliar with how the instance()
 method works, see the Apache::Request documentation.

 If you don't want to use Apache::Request you should be able to subclass
 this module and override its data() method. The data() method should
 return either a hash reference or an object that has a CGI.pm-style
 param() interface.

 BUGS
 May want to allow specific forms to be targeted by name and use separate
 data sources for each.

 Warning: This interface is experimental and may change based on
 experience and feedback.

 AUTHOR
 Copyright 2002, Maurice Aubrey [EMAIL PROTECTED]. All rights
 reserved.

 This module is free software; you may redistribute it and/or modify it
 under the same terms as Perl itself.

 SEE ALSO
 perl(1), mod_perl(3), Apache(3), Apache::Filter(3), HTML::FillInForm(3),
 Apache::Request(3)




RE: loss of shared memory in parent httpd

2002-03-17 Thread Eric Frazier

Hi,

I had hoped that FreeBSD would be immune, but it seems not. I have been
bashing it with http_load and all of a sudden(after a LOT of bashing and
swaping)  all of my processes had zero shared. It did take me days of
fiddling to run into this though. 

Thanks,

Eric 

At 04:16 PM 3/16/02 -0500, Ed Grimm wrote:
I believe I have the answer...

The problem is that the parent httpd swaps, and any new children it
creates load the portion of memory that was swaped from swap, which does
not make it copy-on-write.  The really annoying thing - when memory gets
tight, the parent is the most likely httpd process to swap, because its
memory is 99% idle.  This issue aflicts Linux, Solaris, and a bunch of
other OSes.

The solution is mlockall(2), available under Linux, Solaris, and other
POSIX.1b compliant OSes.  I've not experimented with calling it from
perl, and I've not looked at Apache enough to consider patching it
there, but this system call, if your process is run as root, will
prevent any and all swapping of your process's memory.  If your process
is not run as root, it returns an error.


The reason turning off swap works is because it forces the memory from
the parent process that was swapped out to be swapped back in.  It will
not fix those processes that have been sired after the shared memory
loss, as of Linux 2.2.15 and Solaris 2.6.  (I have not checked since
then for behavior in this regard, nor have I checked on other OSes.)

Ed

On Thu, 14 Mar 2002, Bill Marrs wrote:

 It's copy-on-write.  The swap is a write-to-disk.
 There's no such thing as sharing memory between one process on disk(/swap)
 and another in memory.
 
 agreed.   What's interesting is that if I turn swap off and back on again, 
 the sharing is restored!  So, now I'm tempted to run a crontab every 30 
 minutes that  turns the swap off and on again, just to keep the httpds 
 shared.  No Apache restart required!

 Seems like a crazy thing to do, though.
 
 You'll also want to look into tuning your paging algorithm.
 
 Yeah... I'll look into it.  If I had a way to tell the kernel to never swap 
 out any httpd process, that would be a great solution.  The kernel is 
 making a bad choice here.  By swapping, it triggers more memory usage 
 because sharing removed on the httpd process group (thus multiplied)...
 
 I've got MaxClients down to 8 now and it's still happening.  I think my 
 best course of action may be a crontab swap flusher.
 
 -bill


http://www.kwinternet.com/eric
(250) 655 - 9513 (PST Time Zone)






Re: Trouble w/ LWP during mod_perl install

2002-03-17 Thread Ged Haywood

Hi there,

On Sun, 17 Mar 2002, John Kolvereid wrote:

 I got your name from the mod_perl mailing list,

Please post to the list, not to an individual member, unless you are
replying to a message from that member on the list - in which case you
should normally cc the list.  (You will find more help about this kind
of thing in http://perl.apache.org/email-etiquette and there are some
links in there to other documents you should also read... :)

 I am trying to install mod_perl-1.26 on Linux RedHat 6.2 w/
 Apache-1.3.22.  I am using the following build file:
   perl Makefile.PL \
   APACHE_PREFIX=/usr/local/apache \
   APACHE_SRC=/home/ssl/apache_1.3.22 \
   DO_HTTPD=1 \
   USE_APACI=1 \
   EVERYTHING=1
 
 I get a lot of messages,

That's normal.  You haven't said where you have put the mod_perl
source, can I assume that it is /home/ssl/mod_perl-1.26?

 then I run 'make', and 'make test'.
 Problem is that make test complains that it cannot find LWP.

It isn't absolutely necessary but it's a good idea to get 'make test'
to run successfully, which needs LWP.

 I downloaded and installed (I think) libwww-perl-5.64.

How did you do that?  It's probably easiest to use CPAN.pm:

perl -MCPAN -eshell

 Unfortunately, it didn't seem to resolve my LWP problem.  When I do
 a 'make install' nothing seems to change.

H.  You aren't helping me very much there.  Are you following all
the instructions carefully?  What happens?

'make install' doesn't rely on LWP.  You probably need to be root to
'make install'.  Do you think you have successfully compiled a binary
after the 'make' step?  It will be called 'httpd'.  Check the date and
time of the binary to make sure it's the one you've built and not just
one that was lying around in there from an old installation.  Can you
run it with 'httpd -l' and post the result?

73,
Ged.





ANNOUNCE: Bricolage 1.2.3

2002-03-17 Thread David Wheeler

The Bricolage development team is proud to announce the release of
Bricolage version 1.2.3. This is a maintenance release with many bug
fixes. It replaces the 1.2.2 release, which , due to a packaging error,
was a broken distribution. All Bricolage 1.1.x and 1.2.x users are
strongly encouraged to upgrade to this version in order to take
advantage of its greater stability and reliability.

Here's a brief description of Bricolage:

Bricolage is a full-featured, open-source, enterprise-class content
management system. It offers a browser-based interface for ease-of
use, a full-fledged templating system with complete programming
language support for flexibility, and many other features. It 
operates in an Apache/mod_perl environment, and uses the PostgreSQL 
RDBMS for its repository.

More information on Bricolage can be found on its home page.

  http://bricolage.thepirtgroup.com/

And it can be downloaded from SourceForge.

  http://sourceforge.net/project/showfiles.php?group_id=34789

--The Bricolage Team

-- 
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/  Yahoo!: dew7e
   Jabber: [EMAIL PROTECTED]



Re: [ANNOUNCE] The New mod_perl logo - results now in...

2002-03-17 Thread Steve Piner



Mark Fowler wrote:
 
 On Fri, 15 Mar 2002, Jonathan M. Hollin wrote:
 
  However, I request your comments on this idea:  should we have just one
  button (helping to develop a distinct identity for mod_perl) or should
  we have several (for choice)?  It's up to you...
 
 I think that we need one theme of buttons, to ensure consistent
 branding.  As per my comments when I voted stated, I'd love to see some
 buttons/logos based on the winning logo.  In particular:
 
  - A square button that's just made up of the square cog logo
  - A square button that's just made up of a grey m and a blue p
  - A small rectangle version of the words modperl without the cog
 
 ...you get the idea, variations around a central design
 
 Also, we could do with both a monochrome and a black and white version of
 the logo (for print.)
 
 Is the logo available in a vector file format so that we can easily make
 scaled copies of it?  Or are we restricted to the pixel banners that
 currently exist?
 
 Later.
 
 Mark.
 
 --
 s''  Mark Fowler London.pm   Bath.pm
  http://www.twoshortplanks.com/  [EMAIL PROTECTED]
 ';use Term'Cap;$t=Tgetent Term'Cap{};print$t-Tputs(cl);for$w(split/  +/
 ){for(0..30){$|=print$t-Tgoto(cm,$_,$y). $w;select$k,$k,$k,.03}$y+=2}


I definitely agree with this. I'd like to see some more colour
variations (maybe just background colours even) to allow it to fit into
a site's design better.

Jonathan asked whether we should have just one button, or several. I'd
say just one theme, with several variations as mentioned above.

Others have suggested several buttons and I'm assuming they mean with
differing themes. I'm against that, as the point of a logo is to
reinforce the branding of mod_perl. Of course, if people don't want to
use this theme, they won't. That's fine. That's no worse than the
current situation.

Finally, I think the mod_perl/modperl/ModPerl/Mod_perl thing is a
non-issue. We all know what is being talked about, right? It's nowhere
near as bad as the .gif hard 'G' or soft 'G' or the vi V.I. versus
'vie' problems.

Steve

-- 
Steve Piner
Web Applications Developer
Marketview Limited
http://www.marketview.co.nz



Re: [ANNOUNCE] The New mod_perl logo - results now in...

2002-03-17 Thread Matt Sergeant

On Mon, 18 Mar 2002, Steve Piner wrote:

 I definitely agree with this. I'd like to see some more colour
 variations (maybe just background colours even) to allow it to fit into
 a site's design better.

 Jonathan asked whether we should have just one button, or several. I'd
 say just one theme, with several variations as mentioned above.

This is dead easy to do with the SVG version. Feel free to hack around
with it.

-- 
!-- Matt --
:-Get a smart net/:-




Re: Trouble w/ LWP during mod_perl install

2002-03-17 Thread Ade Olonoh

 Then I try running
  /usr/local/apache/bin/apachectl startssl
 
 Unfortunately I get the msg:
   Syntax error on line 206 of   
 /usr/local/apache/conf/httpd.conf:
   Invalid command 'LoadModule', perhaps mis-spelled or
   defined by a module not included in the server
 configuration
   could not locate Module SSL (line 206 httpd.conf)

Are you installing on top of an existing Apache directory?  In other
words, was /usr/local/apache/conf/httpd.conf created by the install, or
did it already exist before you built Apache?  It looks like the conf
file might expect Apache to have been built with DSO support but it
wasn't in actuality.

In case you haven't seen this already, you might take a look at this
guide to installing Apache with mod_perl and mod_ssl:
http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_ 
The options it suggests should work for you here.


--Ade.



Re: [ANNOUNCE] Apache::FillInForm

2002-03-17 Thread Ade Olonoh

 httpd.conf:
 
   PerlModule Apache::Filter
   PerlModule Apache::FillInForm
   FilesMatch \.foo$
 PerlSetVar Filter on
 PerlHandler Apache::RegistryFilter Apache::FillInForm
   /FilesMatch
 
 And then somewhere in your application:
 
   use Apache::FillInForm;
   Apache::FillInForm-fill; # We have a form to fill out


Excuse my ignorance, but I'm a bit confused.  From this example, would
test.foo be an HTML file, or a Perl program?  

If the former, in what what application would you call fill()?  

If the latter, is the Apache conf to tell Apache::Filter to fill in
whatever form it finds in the Perl program's output?


--Ade.





Re: Trouble w/ LWP during mod_perl install

2002-03-17 Thread John Kolvereid

Hi Ade,
  I followed your suggestion and went to 
http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_

  Most of their steps I had followed before.  Now I
tried to config mod_perl w/ the following config file
as they had suggested:
  perl Makefile.PL \
  APACHE_PREFIX=/usr/local/apache \
  APACHE_SRC=/home/ssl/apache_1.3.22 \
  SSL_BASE=/usr/local/ssl \
  APACI_ARGS='--enable-module=ssl, \
  --enable-shared=ssl, \
  --enable-module=proxy, \
  --enable-shared=proxy, \
  --prefix=/usr/local/apache, \
  --enable-module=rewrite' \
  DO_HTTPD=1 \
  USE_APACI=1 \
  EVERYTHING=1

when I try to do a 'make' I get errors such as 
  *** No rule to make target 'all'. Stop
I can get it to make and make install if I leave out
the APACI_ARGS, but then it doesn't know how to create
Apache w/ ssl.
  Yes I do have an existing Apache which I created w/
mod_ssl.  It has been working fine.  My goal is to add
mod_perl.  Any suggestions.  Please advise.

  Thanks.
   John Kolvereid

--- Ade Olonoh [EMAIL PROTECTED] wrote:
  Then I try running
   /usr/local/apache/bin/apachectl startssl
  
  Unfortunately I get the msg:
Syntax error on line 206 of   
  /usr/local/apache/conf/httpd.conf:
Invalid command 'LoadModule', perhaps
 mis-spelled or
defined by a module not included in the server  
  
  configuration
could not locate Module SSL (line 206
 httpd.conf)
 
 Are you installing on top of an existing Apache
 directory?  In other
 words, was /usr/local/apache/conf/httpd.conf created
 by the install, or
 did it already exist before you built Apache?  It
 looks like the conf
 file might expect Apache to have been built with DSO
 support but it
 wasn't in actuality.
 
 In case you haven't seen this already, you might
 take a look at this
 guide to installing Apache with mod_perl and
 mod_ssl:

http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_
 
 The options it suggests should work for you here.
 
 
 --Ade.


__
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/



RE: Trouble w/ LWP during mod_perl install

2002-03-17 Thread OCNS Consulting

John,

Consider building mod_perl as a DSO outside of Apache. Look for the 
section title Build mod_perl as DSO outside Apache source tree via 
APXS in the file INSTALL.apaci.

This should work for you. Let us know.

RB

-Original Message-
From: John Kolvereid [mailto:[EMAIL PROTECTED]]
Sent: Sunday, March 17, 2002 6:09 PM
To: Ade Olonoh
Cc: mod_perl Mailing List
Subject: Re: Trouble w/ LWP during mod_perl install


Hi Ade,
  I followed your suggestion and went to 
http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_

  Most of their steps I had followed before.  Now I
tried to config mod_perl w/ the following config file
as they had suggested:
  perl Makefile.PL \
  APACHE_PREFIX=/usr/local/apache \
  APACHE_SRC=/home/ssl/apache_1.3.22 \
  SSL_BASE=/usr/local/ssl \
  APACI_ARGS='--enable-module=ssl, \
  --enable-shared=ssl, \
  --enable-module=proxy, \
  --enable-shared=proxy, \
  --prefix=/usr/local/apache, \
  --enable-module=rewrite' \
  DO_HTTPD=1 \
  USE_APACI=1 \
  EVERYTHING=1

when I try to do a 'make' I get errors such as 
  *** No rule to make target 'all'. Stop
I can get it to make and make install if I leave out
the APACI_ARGS, but then it doesn't know how to create
Apache w/ ssl.
  Yes I do have an existing Apache which I created w/
mod_ssl.  It has been working fine.  My goal is to add
mod_perl.  Any suggestions.  Please advise.

  Thanks.
   John Kolvereid

--- Ade Olonoh [EMAIL PROTECTED] wrote:
  Then I try running
   /usr/local/apache/bin/apachectl startssl
  
  Unfortunately I get the msg:
Syntax error on line 206 of   
  /usr/local/apache/conf/httpd.conf:
Invalid command 'LoadModule', perhaps
 mis-spelled or
defined by a module not included in the server  
  
  configuration
could not locate Module SSL (line 206
 httpd.conf)
 
 Are you installing on top of an existing Apache
 directory?  In other
 words, was /usr/local/apache/conf/httpd.conf created
 by the install, or
 did it already exist before you built Apache?  It
 looks like the conf
 file might expect Apache to have been built with DSO
 support but it
 wasn't in actuality.
 
 In case you haven't seen this already, you might
 take a look at this
 guide to installing Apache with mod_perl and
 mod_ssl:

http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_
 
 The options it suggests should work for you here.
 
 
 --Ade.


__
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/




Re: Trouble w/ LWP during mod_perl install

2002-03-17 Thread Ade Olonoh

   Most of their steps I had followed before.  Now I
 tried to config mod_perl w/ the following config file
 as they had suggested:
   perl Makefile.PL \
   APACHE_PREFIX=/usr/local/apache \
   APACHE_SRC=/home/ssl/apache_1.3.22 \
   SSL_BASE=/usr/local/ssl \
   APACI_ARGS='--enable-module=ssl, \
 --enable-shared=ssl, \
 --enable-module=proxy, \
 --enable-shared=proxy, \
 --prefix=/usr/local/apache, \
 --enable-module=rewrite' \
   DO_HTTPD=1 \
   USE_APACI=1 \
   EVERYTHING=1
 
 when I try to do a 'make' I get errors such as 
   *** No rule to make target 'all'. Stop

Can you send the full output after you run the perl Makefile.PL
above?  There might be some errors there that would give a hint to why
it's not working.

--Ade.



Re: [ANNOUNCE] Apache::FillInForm

2002-03-17 Thread Maurice Aubrey

On Sun, Mar 17, 2002 at 04:27:21PM +, Mark Maunder wrote:
 Why not just use HTML::FillInForm?
 Maurice Aubrey wrote:
  http://www.creation.com/~maurice/Apache-FillInForm-0.01.tar.gz

This is just a wrapper, similar to Apache::Clean, that makes it simpler
in certain situations.  If your content handler buffers its output and you can
pass it directly through HTML::FillInForm yourself then great.

Maurice



Re: [ANNOUNCE] Apache::FillInForm

2002-03-17 Thread Maurice Aubrey

On Sun, Mar 17, 2002 at 05:19:37PM -0500, Ade Olonoh wrote:
  httpd.conf:
  
PerlModule Apache::Filter
PerlModule Apache::FillInForm
FilesMatch \.foo$
  PerlSetVar Filter on
  PerlHandler Apache::RegistryFilter Apache::FillInForm
/FilesMatch
  
  And then somewhere in your application:
  
use Apache::FillInForm;
Apache::FillInForm-fill; # We have a form to fill out
 
 
 Excuse my ignorance, but I'm a bit confused.  From this example, would
 test.foo be an HTML file, or a Perl program?  

A perl program (e.g., a registry script, content handler,
templating system, etc.).

 If the former, in what what application would you call fill()?  
 
 If the latter, is the Apache conf to tell Apache::Filter to fill in
 whatever form it finds in the Perl program's output?

The apache conf just places it in the chain.  Calling Apache::FillInForm-fill
(in the perl code) is what activates the filter for a particular request.
  
It's equivalent to how Apache::ASP works.  If you set $Response-{FormFill} = 1
in a template, Apache::ASP filters the output through HTML::FillInForm.  This is
the same idea except it's largely decoupled from the content generation system.

Maurice



Re: Trouble w/ LWP during mod_perl install

2002-03-17 Thread Ged Haywood

Hi there,

On Sun, 17 Mar 2002, John Kolvereid wrote:

   In order to try and install mod_perl-1.26 in RedHat
 6.2 w/ Apache 1.3.22 I, as ROOT, run the following
 in my /home/ssl/mod_perl-1.26:
  perl Makefile.PL \
[snip]
[snip]
 Then I try running
  /usr/local/apache/bin/apachectl startssl

I think you're getting confused with too many Apache modules.  Try to
build without ssl to begin with, so that you can check that what
you're doing for mod_perl is OK.

Please read the installation section of the Guide and follow the
instructions carefully.  You will see that it suggests that you do the
'make' and 'make test' steps NOT as root, then 'make install' as root.
It's not unknown for things to get a little screwy if you try to build
as root, and especially if sometimes you're logged in as root and
sometimes you're not.  It might be best if you delete the source trees
in /home/ssl/mod_perl-1.26 and /home/ssl/apache_1.3.22 and start
again, or start again in a new directory, say something like this:

$ cd /home/fred/src/apache_1.3.22/
$ tar xzvf .../apache_1.3.22.tar.gz
$ cd /home/fred/src/mod_perl-1.26/
$ tar xzvf .../mod_perl-1.26.tar.gz
$ cp makepl_args.mod_perl .
$ perl Makefile.PL
$ make
$ su
# make install
# ls -l /usr/local/sbin/httpd
... (Check here that the date and time of the binary look sensible:)
# /usr/local/sbin/httpd -f /usr/local/apache/conf/httpd.conf
# tail /usr/local/apache/logs/error_log
... (Check that Apache started and that it says it's a mod_perl Apache:)

The file makepl_args.mod_perl is below, and there is a sample in the
mod_perl/eg directory too.  You might want to adjust these a little to
suit your needs.  You can also put the file in the home directory of
the user who does 'make' but then you need to prefix the filename with
a dot, i.e. .makepl_args.mod_perl.

   Invalid command 'LoadModule', perhaps mis-spelled or
   defined by a module not included in the server
 configuration
   could not locate Module SSL (line 206 httpd.conf)
 
 My only recourse is then to rebuild Apache w/o mod_perl.

This error has nothing to do with mod_perl.  You have a 'loadmodule'
directive in httpd.conf but you don't have mod_so.c compiled into the
Apache which you are trying to start using that httpd.conf - as you
will see if you will get the output of 'httpd -l' as I asked you to do
in my previous message.  Try to understand what you're doing, it's not
really that complicated if you are methodical.  You are going to build
a binary called 'httpd' and you can run it without 'apachectl'.  This
is a script that does some other stuff too.  You can try for example
'apachectl configtest'.  'apachectl' is created by 'make install'.
You need to check that it is starting the right Apache, i.e. the one
you just built!  Be careful, there may be several of them (both httpd
and apachectl) kicking around if you have been trying lots of builds
in desperation...

 I am having a great deal of difficulty installing mod_perl.  I am
 not sure it is worth it.

It's worth it but you will have to do quite a bit of reading and it
won't all happen overnight.  Your difficulties at the moment do not
seem to stem primarily from mod_perl itself.

   I have been reading installation excerpts frm various sources

...and then you have to do what it says in the things you've read. :)

 w/ Perl and C', and the internet CPAN sites.  My build in

?  Your message seems to have been truncated here.

73,
Ged.

8--
USE_APACI=1
APACHE_PREFIX=/usr/local
APACHE_SRC=../apache_1.3.12/src
DO_HTTPD=1
EVERYTHING=1
ALL_HOOKS=1
PERL_SSI=1
PERL_SECTIONS=1
APACI_ARGS=--sbindir=/usr/local/sbin/
APACI_ARGS=--sysconfdir=/usr/local/apache/conf
APACI_ARGS=--runtimedir=/usr/local/apache/run
APACI_ARGS=--logfiledir=/usr/local/apache/logs
8--




Re: Trouble w/ LWP during mod_perl install

2002-03-17 Thread John Kolvereid

Hi Ade,
   I am sending the errs as an attachment.  Thanks.
 John Kolvereid
--- Ade Olonoh [EMAIL PROTECTED] wrote:
Most of their steps I had followed before.  Now
 I
  tried to config mod_perl w/ the following config
 file
  as they had suggested:
perl Makefile.PL \
APACHE_PREFIX=/usr/local/apache \
APACHE_SRC=/home/ssl/apache_1.3.22 \
SSL_BASE=/usr/local/ssl \
APACI_ARGS='--enable-module=ssl, \
--enable-shared=ssl, \
--enable-module=proxy, \
--enable-shared=proxy, \
--prefix=/usr/local/apache, \
--enable-module=rewrite' \
DO_HTTPD=1 \
USE_APACI=1 \
EVERYTHING=1
  
  when I try to do a 'make' I get errors such as 
*** No rule to make target 'all'. Stop
 
 Can you send the full output after you run the perl
 Makefile.PL
 above?  There might be some errors there that would
 give a hint to why
 it's not working.
 
 --Ade.


__
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/

Will configure via APACI
cp apaci/Makefile.libdir ../apache_1.3.22/src/modules/perl/Makefile.libdir
cp apaci/Makefile.tmpl ../apache_1.3.22/src/modules/perl/Makefile.tmpl
cp apaci/README ../apache_1.3.22/src/modules/perl/README
cp apaci/configure ../apache_1.3.22/src/modules/perl/configure
cp apaci/libperl.module ../apache_1.3.22/src/modules/perl/libperl.module
cp apaci/mod_perl.config.sh ../apache_1.3.22/src/modules/perl/mod_perl.config.sh
cp apaci/load_modules.pl ../apache_1.3.22/src/modules/perl/load_modules.pl
cp apaci/find_source ../apache_1.3.22/src/modules/perl/find_source
cp apaci/apxs_cflags ../apache_1.3.22/src/modules/perl/apxs_cflags
cp apaci/perl_config ../apache_1.3.22/src/modules/perl/perl_config
cp apaci/mod_perl.exp ../apache_1.3.22/src/modules/perl/mod_perl.exp
PerlDispatchHandler.enabled
PerlChildInitHandlerenabled
PerlChildExitHandlerenabled
PerlPostReadRequestHandler..enabled
PerlTransHandlerenabled
PerlHeaderParserHandler.enabled
PerlAccessHandler...enabled
PerlAuthenHandler...enabled
PerlAuthzHandlerenabled
PerlTypeHandler.enabled
PerlFixupHandlerenabled
PerlHandler.enabled
PerlLogHandler..enabled
PerlInitHandler.enabled
PerlCleanupHandler..enabled
PerlRestartHandler..enabled
PerlStackedHandlers.enabled
PerlMethodHandlers..enabled
PerlDirectiveHandlers...enabled
PerlTableApienabled
PerlLogApi..enabled
PerlUriApi..enabled
PerlUtilApi.enabled
PerlFileApi.enabled
PerlConnectionApi...enabled
PerlServerApi...enabled
PerlSectionsenabled
PerlSSI.enabled
Will run tests as User: 'nobody' Group: 'root'
(cd ../apache_1.3.22  CC=cc ./configure 
--activate-module=src/modules/perl/libperl.a --disable-rule=EXPAT --enable-module=ssl  
\
  --enable-shared=ssl  \
  --enable-module=proxy  \
  --enable-shared=proxy  \
  --prefix=/usr/local/apache  \
  --enable-module=rewrite)
Configuring for Apache, Version 1.3.22
 + using installation path layout: Apache (config.layout)
 + activated perl module (modules/perl/libperl.a)
Creating Makefile
Creating Configuration.apaci in src
 + enabling mod_so for DSO support
Creating Makefile in src
 + configured for Linux platform
 + setting C pre-processor to cc -E
 + checking for system header files
 + adding selected modules
o rewrite_module uses ConfigStart/End
 + using -lndbm for DBM support
  enabling DBM support for mod_rewrite
o ssl_module uses ConfigStart/End
  + SSL interface: mod_ssl/2.8.5
  + SSL interface build type: DSO
  + SSL interface compatibility: enabled
  + SSL interface experimental code: disabled
  + SSL interface conservative code: disabled
  + SSL interface vendor extensions: disabled
  + SSL interface plugin: Built-in SDBM
  + SSL library path: /usr/local/ssl
  + SSL library version: SSLeay 0.9.0b 29-Jun-1998
Error: OpenSSL VERSIONS BELOW 0.9.3 ARE NO LONGER SUPPORTED.
Hint:  Use OpenSSL version 0.9.3 or higher!
Checking CGI.pm VERSION..ok
Checking for LWP::UserAgent..failed
Can't locate URI.pm in @INC (@INC contains: ./lib /usr/lib/perl5/5.00503/i386-linux 
/usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux 
/usr/lib/perl5/site_perl/5.005 .) at (eval 2) line 3.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.005/LWP/UserAgent.pm 
line 108.

The libwww-perl library is needed to run the test suite.
Installation of this library is recommended, but not required.

Checking for HTML::HeadParserfailed
Can't locate HTML/HeadParser.pm in @INC (@INC contains: ./lib 
/usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 

RE: Trouble w/ LWP during mod_perl install

2002-03-17 Thread John Kolvereid

Hi RB,
  Here is the configuration I tried:
perl Makefile.PL \
APACHE_PREFIX=/usr/local/apache \
APACHE_SRC=/home/ssl/apache_1.3.22 \
USE_APXS=1 \
WITH_APXS=/usr/local/apache/bin/apxs \
DO_HTTPD=1 \
USE_APACI=1 \
EVERYTHING=1
Both w/ and w/o the APACHE_PRFIX and APACHE_SRC lines.
The errors are attached.  Please advise.  Thanks.
--- OCNS Consulting [EMAIL PROTECTED] wrote:
 John,
 
 Consider building mod_perl as a DSO outside of
 Apache. Look for the 
 section title Build mod_perl as DSO outside Apache
 source tree via 
 APXS in the file INSTALL.apaci.
 
 This should work for you. Let us know.
 
 RB
 
 -Original Message-
 From: John Kolvereid [mailto:[EMAIL PROTECTED]]
 Sent: Sunday, March 17, 2002 6:09 PM
 To: Ade Olonoh
 Cc: mod_perl Mailing List
 Subject: Re: Trouble w/ LWP during mod_perl install
 
 
 Hi Ade,
   I followed your suggestion and went to 

http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_
 
   Most of their steps I had followed before.  Now I
 tried to config mod_perl w/ the following config
 file
 as they had suggested:
   perl Makefile.PL \
   APACHE_PREFIX=/usr/local/apache \
   APACHE_SRC=/home/ssl/apache_1.3.22 \
   SSL_BASE=/usr/local/ssl \
   APACI_ARGS='--enable-module=ssl, \
 --enable-shared=ssl, \
 --enable-module=proxy, \
 --enable-shared=proxy, \
 --prefix=/usr/local/apache, \
 --enable-module=rewrite' \
   DO_HTTPD=1 \
   USE_APACI=1 \
   EVERYTHING=1
 
 when I try to do a 'make' I get errors such as 
   *** No rule to make target 'all'. Stop
 I can get it to make and make install if I leave out
 the APACI_ARGS, but then it doesn't know how to
 create
 Apache w/ ssl.
   Yes I do have an existing Apache which I created
 w/
 mod_ssl.  It has been working fine.  My goal is to
 add
 mod_perl.  Any suggestions.  Please advise.
 
   Thanks.
John Kolvereid
 
 --- Ade Olonoh [EMAIL PROTECTED] wrote:
   Then I try running
/usr/local/apache/bin/apachectl startssl
   
   Unfortunately I get the msg:
 Syntax error on line 206 of   
   /usr/local/apache/conf/httpd.conf:
 Invalid command 'LoadModule', perhaps
  mis-spelled or
 defined by a module not included in the server
  
   
   configuration
 could not locate Module SSL (line 206
  httpd.conf)
  
  Are you installing on top of an existing Apache
  directory?  In other
  words, was /usr/local/apache/conf/httpd.conf
 created
  by the install, or
  did it already exist before you built Apache?  It
  looks like the conf
  file might expect Apache to have been built with
 DSO
  support but it
  wasn't in actuality.
  
  In case you haven't seen this already, you might
  take a look at this
  guide to installing Apache with mod_perl and
  mod_ssl:
 

http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_
  
  The options it suggests should work for you here.
  
  
  --Ade.
 
 
 __
 Do You Yahoo!?
 Yahoo! Sports - live college hoops coverage
 http://sports.yahoo.com/
 


__
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/


bld2.err
Description: bld2.err


Re: Trouble w/ LWP during mod_perl install

2002-03-17 Thread Stas Bekman

John Kolvereid wrote:
 Hi Ade,
I am sending the errs as an attachment.  Thanks.

It helps to actually *look* at the build log:

 Will configure via APACI
...
 o ssl_module uses ConfigStart/End
   + SSL interface: mod_ssl/2.8.5
   + SSL interface build type: DSO
   + SSL interface compatibility: enabled
   + SSL interface experimental code: disabled
   + SSL interface conservative code: disabled
   + SSL interface vendor extensions: disabled
   + SSL interface plugin: Built-in SDBM
   + SSL library path: /usr/local/ssl
   + SSL library version: SSLeay 0.9.0b 29-Jun-1998
 Error: OpenSSL VERSIONS BELOW 0.9.3 ARE NO LONGER SUPPORTED.
 Hint:  Use OpenSSL version 0.9.3 or higher!

hint, hint: install openssl 0.9.3 or higher!

 Checking for LWP::UserAgent..failed
 Can't locate URI.pm in @INC (@INC contains: ./lib /usr/lib/perl5/5.00503/i386-linux 
/usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux 
/usr/lib/perl5/site_perl/5.005 .) at (eval 2) line 3.
 BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.005/LWP/UserAgent.pm 
line 108.
 
 The libwww-perl library is needed to run the test suite.
 Installation of this library is recommended, but not required.
 
 Checking for HTML::HeadParserfailed
 Can't locate HTML/HeadParser.pm in @INC (@INC contains: ./lib 
/usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 
/usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005 .) at 
Makefile.PL line 1154.
 
 The HTML-Parser package is needed (by libwww-perl) to run the test suite.

install URI and HTML::HeadParser packages.

Most likely you've installed an RPM or a similar package of libwww-perl 
without installing its prerequisites.

Do:

perl -MCPAN -eshell
cpan install URI HTML::HeadParser LWP

need to specify explicitly since LWP is already installed.

and 'make test' should work.



_
Stas Bekman JAm_pH  --   Just Another mod_perl Hacker
http://stason.org/  mod_perl Guide   http://perl.apache.org/guide
mailto:[EMAIL PROTECTED]  http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/




LWP::Parallel error

2002-03-17 Thread Parag R Naik



I get the following error . can any 
body help .i install ParallelUserAgent-2.51.tar.gz does it require some additional modules 
.


Can't locate object method "new" via package 
"LWP::Parallel::Protocol::http::Socket"
Regards

Parag R NaikPhone : 5093100(off)

Tough times dont last for a long tough people 
always do.

To send secure email get my certificate from 
:http://parag.freeshell.org/parag2.p7b


Re: loss of shared memory in parent httpd (2)

2002-03-17 Thread Eric Frazier

Hi,

This may be totaly ignorate crap, but I noticed this when I was reading the
ps man page on BSD 4.5 about sys/proc.h flags

This one I noticed.. 

P_SYSTEM   0x00200System proc: no sigs, stats or swapping


Could this mean what I think it means? That a process with this flag set,
won't be swaped out?? 


Thanks,

Eric 

At 03:55 PM 3/12/02 +0100, Elizabeth Mattijsen wrote:
Oops. Premature sending...

I have two ideas that might help:
- reduce number of global variables used, less memory pollution by lexicals
- make sure that you have the most up-to-date (kernel) version of your 
OS.  Newer Linux kernels seem to be a lot savvy at handling shared memory 
than older kernels.

Again, I wish you strength in fixing this problem...


Elizabeth Mattijsen


http://www.kwinternet.com/eric
(250) 655 - 9513 (PST Time Zone)