Re: Image manipulation recommendation?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 28 June 2002 13:29, Goehring, Chuck Mr., RCI - San Diego wrote: Ryan, I couldn't get the requisites for the gd.pm and related modules to work on Windows. Although these things apparently have worked great for years on UNIX, they may have problems on Windows 2000 servers. I had to go to a purchased Java product that is accessible via a servlet to get graphs generated. Hey Chuck, Assuming you are running ActivePerl, there is a PPM for GDGraph available from the main ActiveState repository (http://www.activestate.com/PPMPackages/5.6). What sort of dependency issues are you running into? Ian -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9HZB6AjpHQQmBAUMRAlHeAKCN/wbIHMWx7w6EdkRd2QaQC19vhwCfcj9Z Ddr++uZE64ayDb3PBX4T6Gc= =99gO -END PGP SIGNATURE-
Re: Naming convention for Apache 2 modules.
On 2002.06.18 09:57 Stas Bekman wrote: [CC'ing Andreas again] Stas is right. The only problem I see with MP_INST_APACHE2 is the fact that using the CPAN.pm module to download the module would fetch the newest version of the module, regardless of whether you wanted the one for mod_perl 2.0 or mod_perl 1.0. That's true :( I hope Andreas can make PAUSE index both versions so CPAN.pm will display the two, but for that we need some sort convention so PAUSE can use to decide on. Andreas, any ideas regarding this issue? An alternative approach could involve placing the functionality specific to mod_perl 2.0 in a sub-module, then conditionally importing that submodule depending on the value of $Apache::Registry::VERSION. Ian
Re: Referencing Directives
On 2002.05.28 01:23 Per Einar Ellefsen wrote: Or... maybe you could try using Apache class methods inside Perl sections (like document_root) -- however I think that'd be pretty shaky. Hmm...something to tinker with as time permits... Thanx, Ian
Re: Configuring mod_perl on Debian
On 2002.05.28 04:03 Jeff A wrote: From: Andrew McNaughton [mailto:[EMAIL PROTECTED]] Sent: 27 May 2002 21:02 To: Ian D. Stewart ... You miss most of the advantage of debian's package management if you start building core components independently. Debian looks after you pretty well, but it's a bit of an all or nothing affair. ie it's worth a little effort to stick with the debian packages if you can. I agree with Andrew - getting Apache, Mod_SSL, PHP4 and mod_perl with PHP4/MySQL and mod_perl/mySQL all co-operating is a relative doddle with Debian packaging. Especially in view of the volume of the 'I cant build...' comments on the mod_perl mailing lists. We usually wget the .debs we want installed as a set, into a dir e.g. /usr/local/deb/build date and then do a dpkg -i *.deb apt-get check FYI, these are SOME of the installed packages on our Dev server yes - it's a bit messy, but it's potato flavoured, with woody extras, and we don't seem to have any issues. - apache 1.3.23-1Versatile, high-performance HTTP server apache-common 1.3.23-1Support files for all Apache webservers libapache-mod-ssl 2.8.7-1 Strong cryptography (HTTPS support) libssl0.9.60.9.6c-1SSL shared libraries mysql-client 3.23.46-2 mysql database client binaries mysql-common 3.23.46-2 mysql database common files libmysqlclient 3.23.38-2 mysql database client library perl 5.6.1-7 Larry Wall's Practical Extraction and libperl5.6 5.6.1-7 Shared Perl library. libapache-dbi-perl 0.88-5 Connect apache server to database via libapache-mod-perl 1.26-2 Integration of perl with the Apache web libapache-reload-perl 0.07-1 Reload changed modules in a mod_perl libapache-request-perl 0.33-1 Generic Apache Request Library libapache-session-perl 1.54-1 Perl modules for keeping persistent libapache-ssi-perl 2.16-1 perl Apache::SSI - Implement Server Side libdbd-mysql-perl 1.2216-2 mySQL database interface for Perl libdbi-perl1.21-2 The Perl5 Database Interface by Tim Bunce php4 4.1.2-1 A server-side, HTML-embedded scripting php4-mysql 4.1.2-1 MySQL module for php4 php4-pear 4.1.2-1 PEAR - PHP Extension Application Reposit - Ok. I'll give it a another go. Interestingly, I have not seen a lot of I can't build this messages on modperl, but have seen a fair number of why isn't this working messages on debian-user. Ian
Re: Configuring mod_perl on Debian
On 2002.05.27 11:43 Lucas M. Saud wrote: maybe you can try a chmod 755 in the script...and check the perl path in first line of the script...and set the directory permission to 777 Tried all of those. Still no good. I've downloaded the source for both Apache and mod_perl, and will be building from scratch. If that works, that I well chock it up to a debian packaging/configuration issue. Thanx for the feedback, Ian
Re: Configuring mod_perl on Debian
On 2002.05.27 12:57 Andrew McNaughton wrote:
Sounds to me like you're not setting your content-type correctly for
some
reason. Have a look at the headers being sent out. It's either not
sending this header, or it's sending something the browser doesn't
know
what to do with.
This is the content of test.pl
BEGIN-SCRIPT
--
#!/usr/bin/perl
# your httpd.conf should have something like this:
# Alias /perl/ /real/path/to/perl-scripts/
# Location /perl
# SetHandler perl-script
# PerlHandler Apache::Registry
# PerlSendHeader On
# Options +ExecCGI
# /Location
print Content-type: text/html\n\n;
print bDate: , scalar localtime, /bbr\n;
print %ENV: br\n, map { $_ = $ENV{$_} br\n } keys %ENV;
--
END-SCRIPT
Based on this, I would expect the content to be set to text/html and
the page to be displayed to be a listing of the current environment.
Galeon identifies the content type as application/x-perl. This would
seem to indicate to me that Apache is serving the script directly
instead of executing the script and serving the output. According to
the mod_perl Guide, the ExecCGI option (which I have set for Location
/perl) is supposed to avoid this situation.
Thanx,
Ian
Re: Configuring mod_perl on Debian
On 2002.05.27 12:59 Eric wrote: On Mon, May 27, 2002 at 12:20:00PM -0400, Ian D. Stewart wrote: On 2002.05.27 11:43 Lucas M. Saud wrote: maybe you can try a chmod 755 in the script...and check the perl path in first line of the script...and set the directory permission to 777 Tried all of those. Still no good. I've downloaded the source for both Apache and mod_perl, and will be building from scratch. If that works, that I well chock it up to a debian packaging/configuration issue. Thanx for the feedback, Ian You said you were using woody (testing)? I haven't been following your problems, but I was able to get apache/mod_perl running on debian with little fuss. What packages have you tried? As a point of reference, these are the apache packages I have installed: % dpkg -l '*apache*' | grep ^i ii apache-common 1.3.24-3 Support files for all Apache webservers ii apache-ssl 1.3.24.2+1.47- Versatile, high-performance HTTP server with ii libapache-mod- 1.26-3 Integration of perl with the Apache web serv ii libapache-requ 0.33-1 Generic Apache Request Library Eric Eric, Here is what I have: dpkg -l '*apache*' | grep '^i' ii apache-common 1.3.24-3 Support files for all Apache webservers ii apache-perl1.3.24-2-1.26- Versatile, high-performance HTTP server with ii libapache-mod- 1.26-3 Integration of perl with the Apache web serv Not sure where our configurations are different (I note you do not have apache-perl installed), but after I installed apache-perl, I had to copy /etc/apache/httpd.conf to /etc/apache-perl/httpd.conf, and make quite a few changes by hand. p.s. you shouldn't ever set a cgi directory to be world-writable (777). Yeah. That struct me as being a bit off... Thanx, Ian
Re: Configuring mod_perl on Debian
On 2002.05.27 12:49 Randy Kobes wrote: I didn't cc the list, as I've lost the original message, but from what I remember, you had Options ExecCGI in a configuration. Does Options +ExecCGI make a difference? Also, as far as I remember, you had PerlSendHeader On Depending on what your script does, and if you use CGI.pm to generate the header, try PerlSendHeader Off Thanx for the feedback Randy. I tried changing both options. Still no good. Thanx Anyways, Ian
Re: Configuring mod_perl on Debian
Well, I haven't had any better luck with the debian package but I have gotten Apache and mod_perl running by building from source. Thanx for all the help, Ian On 2002.05.27 13:06 Ian D. Stewart wrote: On 2002.05.27 12:59 Eric wrote: On Mon, May 27, 2002 at 12:20:00PM -0400, Ian D. Stewart wrote: On 2002.05.27 11:43 Lucas M. Saud wrote: maybe you can try a chmod 755 in the script...and check the perl path in first line of the script...and set the directory permission to 777 Tried all of those. Still no good. I've downloaded the source for both Apache and mod_perl, and will be building from scratch. If that works, that I well chock it up to a debian packaging/configuration issue. Thanx for the feedback, Ian You said you were using woody (testing)? I haven't been following your problems, but I was able to get apache/mod_perl running on debian with little fuss. What packages have you tried? As a point of reference, these are the apache packages I have installed: % dpkg -l '*apache*' | grep ^i ii apache-common 1.3.24-3 Support files for all Apache webservers ii apache-ssl 1.3.24.2+1.47- Versatile, high-performance HTTP server with ii libapache-mod- 1.26-3 Integration of perl with the Apache web serv ii libapache-requ 0.33-1 Generic Apache Request Library Eric Eric, Here is what I have: dpkg -l '*apache*' | grep '^i' ii apache-common 1.3.24-3 Support files for all Apache webservers ii apache-perl1.3.24-2-1.26- Versatile, high-performance HTTP server with ii libapache-mod- 1.26-3 Integration of perl with the Apache web serv Not sure where our configurations are different (I note you do not have apache-perl installed), but after I installed apache-perl, I had to copy /etc/apache/httpd.conf to /etc/apache-perl/httpd.conf, and make quite a few changes by hand. p.s. you shouldn't ever set a cgi directory to be world-writable (777). Yeah. That struct me as being a bit off... Thanx, Ian
Referencing Directives
Is it possible to reference the value of one Directive within another
Directive (e.g., PerlSetVar VariableName ${DocumentRoot}/subdir) ?
Thanx,
Ian
Re: Referencing Directives
On 2002.05.27 15:39 Per Einar Ellefsen wrote:
At 21:13 27.05.2002, Ian D. Stewart wrote:
Is it possible to reference the value of one Directive within
another Directive (e.g., PerlSetVar VariableName
${DocumentRoot}/subdir) ?
If you use Perl sections, yes.
Perl
$DocumentRoot = '/home/httpd/htdocs';
push PerlSetVar, [ VariableName = $DocumentRoot/subdir];
/Perl
Thanx Per. I thought of something like that after I sent out the
message, though wasn't sure of the syntax.
Note that you need to set $DocumentRoot in a Perl section as well.
So Directives declared outside the Perl section (e.g., ServerRoot,
DocumentRoot, etc) are not accessible within the Perl section?
You might want to look at mod_macro too.
Will do.
Thanx,
Ian
Configuring mod_perl on Debian
Dear List, I have been trying for the better part of the day to get Apache w/mod_perl working on a Debian Woody system. With the help of the Configuration section of the mod_perl Guide, I have set up httpd.conf w/ mod_perl support, I have setup a /perl location with Apache::Registry as the PerlHandler, and I have copied a test script from /usr/share/doc/libapache-mod-perl/examples into /perl. However, whenever I try to display http://localhost/perl/test.pl, the browser (Galeon-1.2.1) displays a dialog asking if I want to save the file to disk or open it with an external application. here is the pertinant section of httpd.conf: Alias /perl /var/www/perl PerlModule Apache::Registry Location /perl SetHandler perl-script PerlHandler Apache::Registry Options ExecCGI allow from all PerlSendHeader on /Location Any clues as to what I may be doing wrong, or where to look for more info, would be greatly appreciated. Regards, Ian
