Re: modperl growth
At 11:02 + 2/3/02, Dave Hodgkinson wrote: >Paul DuBois <[EMAIL PROTECTED]> writes: > >> Mac OS X includes Apache, and mod_perl works there, too. That's >> another group of potential new mod_perl-ized servers. > >I think all the recent RedHats come with mod_perl as a DSO by default. I just looked on a RH 7.2 machine. It has the AddModule line in the default httpd.conf, but no mod_perl.so in the modules directory.
Re: modperl growth
At 20:54 -0200 2/2/02, Jorge Godoy wrote: >Matt Sergeant <[EMAIL PROTECTED]> writes: > >> Wow, bizarre. Not sure why but the AxKit list has seen a massive spurt in >> traffic lately too. Perhaps due to the migration to xml.apache.org (well, >> just a link at the moment), but perhaps due to the above? >> >> However I'm always skeptical of such massive changes - perhaps more likely >> is a change in SecuritySpace's methodology? > >You have to remember of the latest attacks on IIS too... People are >migrating from IIS to other web servers. Apache is a very good >candidate to power these ex-IIS sites. > >Since the use of Apache has increased, people start looking after >alternative technologies that use it. mod_perl, AxKit and other are >these technologies. > > >I don't think that this covers all those new servers, but it certainly >covers a lot of them. Mac OS X includes Apache, and mod_perl works there, too. That's another group of potential new mod_perl-ized servers.
RE: Apache::Session Problem -- Addendum
At 10:43 AM + 11/22/01, Jonathan M. Hollin wrote:
>Thank you everyone for the quality of help I've so far received and your
>rapid responses. However... :-(
At the rist of making a shameless plug, you can visit
http://www.kitebird.com/mysql-perl/ and grab the webdb
source distribution there. This accompanies the book
for which the aforementioned URL is the home site. Said
book has a chapter on sessions focusing on Apache::Session,
so you may find the example scripts useful for helping
you solve your problem.
>
>My code now includes:
>
>35: # Session handler...
>36: my %session; undef my $session_id;
>37: use Apache::Session::MySQL;
>38: tie %session, 'Apache::Session::MySQL', $session_id,
>39: { DataSource => 'dbi:mysql:sessions', UserName => 'db_user', Password
>=> 'secret' };
>40: $session_id = "session_id=$session{_session_id};";
>
>I am using Apache-Session v1.54.
>
>The above code generates the following error:
>
>[Thu Nov 22 10:31:38 2001] [error] PerlRun: `Can't connect(
>HASH(0xbdcf54)), no database driver specified and DBI_DSN env var not set at
>E:/Apache/site/lib/Apache/Session/Lock/MySQL.pm line 36 (in cleanup)
>Can't connect( HASH(0x47e2f14)), no database driver specified and DBI_DSN
>env var not set at E:/Apache/site/lib/Apache/Session/Lock/MySQL.pm line 36'
>
>So, as you can see, I've moved on a little - but still don't have a working
>session handler. Any offers?
>
>Note: I know how boring it is to keep reading the same thread - I'll drop
>it if I don't solve this today.
>
>Kindest regards,
>
>Jonathan M. Hollin - WYPUG Co-ordinator
>West Yorkshire Perl User Group
>http://wypug.pm.org/
>
>:: -Original Message-
>:: From: Tatsuhiko Miyagawa [mailto:[EMAIL PROTECTED]]
>:: Sent: 22 November 2001 04:34
>:: To: [EMAIL PROTECTED]
>:: Cc: mod_perl Mailing List
>:: Subject: Re: Apache::Session Problem -- Addendum
>::
>::
>:: On Wed, 21 Nov 2001 23:23:33 -
>:: "Jonathan M. Hollin" <[EMAIL PROTECTED]> wrote:
>::
>:: > 42: tie %session, 'Apache::Session::DBI',
>:: > 43: {DataSource => "dbi:$db_driver:sessions:$db_address"};
>::
>:: put $sid (session id: undef for fresh) after 'Apache::Session::MySQL'.
>::
>:: --
>:: Tatsuhiko Miyagawa <[EMAIL PROTECTED]>
>::
Re: [Announce] MSIISProbes.pm v1.03
>Hello, > >thanks to patches from Brice D. Ruth and others, a new version of >MSIISProbes.pm is available at >http://www.tonkinresolutions.com/MSIISProbes.pm.tar.gz > >Changes: > v1.03 Added code to get e-mail for the SOA of the host >(Brice D. Ruth) > Cut the DNS Resolver's timeout to 20 seconds > > v1.02 Moved the URL for info for each worm into PerlSetVar >in httpd.conf > > >comments/flames welcome No flames, I like it. Is there a way to send a request to the module to have it generate a report on the contents of the cache? > >--nick > > >~~~ >Nick Tonkin
Re: mod_perl memory consumption
At 2:55 PM +1000 8/31/01, Jeremy Howard wrote:
>Paul DuBois wrote:
>> mysql_store_result/mysql_use_result determine whether or not the server
>> sends all the rows to the client at once, or one at a time as the client
>> asks for them. mysql_store_result is therefore more memory intensive
>> for the client (which must hold the entire result set).
>> mysql_use_result is less memory intensive for the client, which needs
>> memory only for one row at a time, but can cause other processes trying
>> to use the server to block, because the tables from which you're
>> retrieving rows are read-locked for the duration of the query (that is,
>> until the client actually fetches the last row).
>>
>For more information see Paul's great book 'MySQL' (New Riders), p257-259.
>If you're not lucky enough to have the book, there's a brief description
>here:
>http://perl.apache.org/guide/databases.html#mysql_use_result_vs_mysql_store
Note that the documentation at this link uses the notation
mysql_store_result() and mysql_use_result(), as though these
things are functions. They aren't. They're statement handle
attributes, typically accessed like this:
$sth->{mysql_store_result} = 1 or 0
$sth->{mysql_use_result} = 1 or 0
Re: mod_perl memory consumption
>[EMAIL PROTECTED] (Perrin Harkins) wrote: >>> I guess that DBI gets all records if you use fetchall_array|hashref >>> and that it is else OK. >> >>No, the behavior that I saw was when fetching a row at a time. Behind the >>scenes, DBI would fetch ALL the rows into RAM and then iterate over them. >>This may have been changed since then. It was a couple of years ago. > >It's still true, mysql will fetch all records at once, whether you ask >for them or not. You can control it with mysql_(use|store)_result, >which is documented as a feature so I think it's not going away anytime >soon. mysql_store_result/mysql_use_result determine whether or not the server sends all the rows to the client at once, or one at a time as the client asks for them. mysql_store_result is therefore more memory intensive for the client (which must hold the entire result set). mysql_use_result is less memory intensive for the client, which needs memory only for one row at a time, but can cause other processes trying to use the server to block, because the tables from which you're retrieving rows are read-locked for the duration of the query (that is, until the client actually fetches the last row). > > > ------ > Ken Williams Last Bastion of Euclidity > [EMAIL PROTECTED]The Math Forum
Re: Repost: Anyone using "virtual server" for mod_perl hosts?
At 2:05 PM -0500 1/30/01, Blue Lang wrote: >On Tue, 30 Jan 2001, Martin Langhoff wrote: > >> There are companies (Verio at least) offering a 'virtual machine' >> running a virtualized OS. Verio is offering NetBSD and Solaris. They >> have a seriouly large iron where many virtual machines run, each virtual >> machine gets a share of CPU, HD and RAM resources, an at least an IP >> address. > >Woah.. I had never heard of this. Have you actually been on a box? I'm >calling them to see if a demo is available. > >My guess would be that no matter how well they slice it, you're still >sharing hardware, and if some guy is running 100 java servlets on the >'real' box that you're sharing, you're gonna have to fight for time. It's >only an extra $60 or so to get a 'real' machine somewhere.. It depends, >like everything else, on your needs. www.digitaldaze.com offers this kind of service, too. You get control over your Apache, smtp, pop, etc. servers. Other people on the machine have their own virtual server, but no access to your own server. (For example, you can't install a CGI script that reads files in my document tree.)
Re: Apache::Registry() and strict
At 10:25 AM +0100 11/7/00, [EMAIL PROTECTED] wrote: >On Tue, 7 Nov 2000, Ron Rademaker wrote: > >Hi, > >> You would think so, however every doc I read (including the one you >> pointed out to me) told me that perl gives me a warning: >> >> Variable $foo will not stay shared at >> >> I do use -w so I should get that warning, but I don't. The variable stays >> defined, but it doesn't have the value of the old variable, it just passes >> the defined($foo) test but the value has changed to an empty array (from a >> full array). > >-w has no effect, read the guide again and use PerlWarn On :-) Please explain, the guide appears to recommend -w as a useful diagnostic technique (and the "Command Line Switches (-w, -T, etc)" section says -w works). > >Bye, >remco > >/--\ >| Remco Schaar | >| e-mail: [EMAIL PROTECTED] | >\--/ > > South Park meets Linux: > - "Oh my God, they killed init!" > - "You bastards!"
