On Thu, 4 Mar 2004, Edouard Lagache wrote:
> Dear mod_perl community,
>
> Randy Kobes <[EMAIL PROTECTED]> wrote at Wed, 3 Mar
> 2004 19:54:47 -0600
> ... snip ...
> >
> >Does it help if you set the APACHE_TEST_STARTUP_TIMEOUT
> >environment variable to, say, 200?
>
> Alas no, it does not, as shown
Philippe M. Chiasson wrote:
On Thu, 2004-03-04 at 14:21 -0800, Stas Bekman wrote:
Philippe M. Chiasson wrote:
On Wed, 2004-03-03 at 18:14 -0800, Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
Hi
I have a problem when my apache_1.3.29 w/ mod_perl 1.29 runs PerlRun
and some CGI scripts with passw
On Thu, 2004-03-04 at 14:21 -0800, Stas Bekman wrote:
> Philippe M. Chiasson wrote:
> > On Wed, 2004-03-03 at 18:14 -0800, Stas Bekman wrote:
> >
> >>[EMAIL PROTECTED] wrote:
> >>
> >>>Hi
> >>>
> >>>I have a problem when my apache_1.3.29 w/ mod_perl 1.29 runs PerlRun
> >>>and some CGI scripts with
Stas Bekman <[EMAIL PROTECTED]> wrote at Thu, 4 Mar 2004 15:23:04 -0800
>But something is telling me that this is not the real problem. The process
>starts but probably it doesn't respond. A simple:
>
>t/TEST -ping
>
>will tell you whether it's really running or just hanging there.
Indeed your h
Edouard Lagache wrote:
Stas Bekman <[EMAIL PROTECTED]> wrote at Thu, 4 Mar 2004 14:24:59 -0800
Edouard Lagache wrote:
... snip ...
waiting 120 seconds for server to start: giving up after 121 secs
!!! server failed to start!
... snip ...
Try:
t/TEST -startup_timeout=600
*Sigh* trying this l
Stas Bekman <[EMAIL PROTECTED]> wrote at Thu, 4 Mar 2004 14:24:59 -0800
>Edouard Lagache wrote:
... snip ...
>waiting 120 seconds for server to start: giving up after 121 secs
>!!! server failed to start!
... snip ...
>
>Try:
>
>t/TEST -startup_timeout=600
*Sigh* trying this literally ca
Geoffrey Young wrote:
my $timeout = $vars->{startup_timeout} ||
$ENV{APACHE_TEST_STARTUP_TIMEOUT} ||
60;
I swapped the order in CVS. thanks.
No, Geoff, the order was correct. Command line options override env vars.
The correct patch seems to be:
Index: lib/
Edouard Lagache wrote:
Dear mod_perl community,
Randy Kobes <[EMAIL PROTECTED]> wrote at Wed, 3 Mar
2004 19:54:47 -0600
... snip ...
waiting 120 seconds for server to start: giving up after 121 secs
!!! server failed to start!
... snip ...
Does it help if you set the APACHE_TEST_STARTUP_TIMEOUT
> my $timeout = $vars->{startup_timeout} ||
> $ENV{APACHE_TEST_STARTUP_TIMEOUT} ||
> 60;
I swapped the order in CVS. thanks.
--Geoff
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiq
Philippe M. Chiasson wrote:
On Wed, 2004-03-03 at 18:14 -0800, Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
Hi
I have a problem when my apache_1.3.29 w/ mod_perl 1.29 runs PerlRun
and some CGI scripts with password encryption.
Script is ...
$password = crypt($password, &mkSalt($name.$password.$v
Dear mod_perl community,
Randy Kobes <[EMAIL PROTECTED]> wrote at Wed, 3 Mar
2004 19:54:47 -0600
... snip ...
>> >waiting 120 seconds for server to start: giving up after 121 secs
>> >!!! server failed to start!
... snip ...
>
>Does it help if you set the APACHE_TEST_STARTUP_TIMEOUT
>environment
Geoffrey Young wrote:
You have the API to do that override already. Add as the first line in
your script:
$r = shift; Apache->request($r);
that's not the same. in mp1 Apache->request is used for pulling $r out of
thin air. isn't +GlobalRequest for that exact circumstance, allowing you to
get at
> You have the API to do that override already. Add as the first line in
> your script:
>
> $r = shift; Apache->request($r);
that's not the same. in mp1 Apache->request is used for pulling $r out of
thin air. isn't +GlobalRequest for that exact circumstance, allowing you to
get at $r when none
Geoffrey Young wrote:
We have the way to do it:
Apache->server->add_config(['PerlOptions +GlobalRequest +SetupEnv']);
But normally, those options are set in httpd.conf's specific containers
and not always globally for the whole server. I'm not sure it's a good
idea to enforce these settings for t
> We have the way to do it:
>
> Apache->server->add_config(['PerlOptions +GlobalRequest +SetupEnv']);
>
> But normally, those options are set in httpd.conf's specific containers
> and not always globally for the whole server. I'm not sure it's a good
> idea to enforce these settings for the whol
Geoffrey Young wrote:
Another thing: In order to make my application to run, for the moment I
use Apache::compat as follows:
PerlModule Apache2
PerlModule Apache::compat
PerlOptions +GlobalRequest
PerlOptions +SetupEnv
Shouldn't PerlOptions +GlobalRequest +SetupEnv be set by default when
using A
>Perhaps you need to rewrite mkSalt() so it supports MD5 salts as well, if
>that's what your system's crypt() expects (?).
Talking of which, I've managed to find a subroutine I wrote that does
exactly this...
#
# generate
At 16:55 2004-03-03 -0800, you wrote:
>I have a problem when my apache_1.3.29 w/ mod_perl 1.29 runs PerlRun
>and some CGI scripts with password encryption.
>$password = crypt($password, &mkSalt($name.$password.$value) );
I'm no expert, but here goes... There are 2 ways of implementing crypt(3):
u
On Thu, 26 Feb 2004 12:29:20 -0800
"Jeffrey W. Baker" <[EMAIL PROTECTED]> wrote:
> On Wed, 2004-02-25 at 16:42, Dave Rolsky wrote:
> > On Wed, 25 Feb 2004, Casey West wrote:
> >
> > > of work for the maintainer in working through the mailing list archives
> >
> > Or maintainer_s_. Why not set u
> ALL OTHER URLS (/) must go to the mode_perl handler
are you 100% sure about that. it's probably really not what you want, but
only you know your application.
but ok, you can do that by setting up
your mod_perl stuff
HTH
--Geoff
--
Report problems: http://perl.apache.org/bugs/
Ma
Jean-Michel Hiver wrote:
>
>> I would consider it a bug, but mod_perl (through the current release)
>> populated %ENV when the first Perl*Handler runs, which may have been
>> before
>> or after translation (which is where path_info becomes known). if you
>> specifically move that PerlInitHandle
On Thu, 2004-03-04 at 08:56, [EMAIL PROTECTED] wrote:
> PerlRun: `Undefined subroutine
> &Apache::ROOT::Scripts::_30311::up_2ecgi::mimeencode called at
> /usr/local/www/data/Scripts//update.cgi line 476.
>
> How does this kind of problem likely happen? Is any bad script in the one
> called by "req
I would consider it a bug, but mod_perl (through the current release)
populated %ENV when the first Perl*Handler runs, which may have been before
or after translation (which is where path_info becomes known). if you
specifically move that PerlInitHandler to a PerlHeaderParserHandler I'd
suspect a
Jean-Michel Hiver wrote:
> Hi List,
>
> I am trying to get a rather large-ish web app to run with apache 2 /
> mod_perl 1.99. I have installed the latest RPMs for Fedora from FreshRPMs.
>
> PerlModule Apache2
> PerlModule Apache::compat
> PerlOptions +GlobalRequest
> PerlOptions +SetupEnv
Hi
I am using mod_perl 1.29 and perl 5.8.0 on apache_1.3.29 running on RedHat
8.0.
CGI scripts have some "require" and some of require are called by PerlRun
but some are not...
So this output following error message below..
PerlRun: `Undefined subroutine
&Apache::RO
Hi List,
I am trying to get a rather large-ish web app to run with apache 2 /
mod_perl 1.99. I have installed the latest RPMs for Fedora from FreshRPMs.
PerlModule Apache2
PerlModule Apache::compat
PerlOptions +GlobalRequest
PerlOptions +SetupEnv
I have a very strange behavior with PerlIni
26 matches
Mail list logo
