--- Perrin Harkins <[EMAIL PROTECTED]> wrote: > On Fri,
2004-07-23 at 18:12, MARTIN MOSS wrote:
> > My question is, If you don't have a PerlModule
> > statement or a use My::Module, or a require or a
> > +My::Module statement so it looks like this
> >
> > #PerlModule My:Module
> >
> > set-handle
Thanks very much Perrin,
Have a nice weekend,
Marty
--- Perrin Harkins <[EMAIL PROTECTED]> wrote: > On Fri,
2004-07-23 at 18:12, MARTIN MOSS wrote:
> > My question is, If you don't have a PerlModule
> > statement or a use My::Module, or a require or a
> > +My::Module statement so it looks like
> > > It is setup like this:-
> > >
> > >
> > > SetHandler perl-script
> > > PerlHandler My::Package
> > >
> > Shouldn't that be
> >PerlHandler My::Package->handler
>
> Technically that isn't necessary if your method is
> called handler() and
> you have prototyped it with ($$).
>
I've go
On Fri, 2004-07-23 at 18:12, MARTIN MOSS wrote:
> My question is, If you don't have a PerlModule
> statement or a use My::Module, or a require or a
> +My::Module statement so it looks like this
>
> #PerlModule My:Module
>
> set-handler PerlScript
> PerlHandler My::Module
>
>
> But the module
On Fri, 2004-07-23 at 00:35, Michael wrote:
> > It is setup like this:-
> >
> >
> > SetHandler perl-script
> > PerlHandler My::Package
> >
> Shouldn't that be
>PerlHandler My::Package->handler
Technically that isn't necessary if your method is called handler() and
you have prototyped it wi
MARTIN MOSS wrote:
Michael <[EMAIL PROTECTED]> wrote:Perrin Harkins
wrote:
On Thu, 2004-07-22 at 11:26, MARTIN MOSS wrote:
This error doesn't occur on machines running the
same code (mirrored
in the same way as the redhat box), it works
perfectly fine.
Has anybody seen this type of error before, i
Michael <[EMAIL PROTECTED]> wrote:Perrin Harkins
wrote:
> On Thu, 2004-07-22 at 11:26, MARTIN MOSS wrote:
>
>>This error doesn't occur on machines running the
same code (mirrored
>>in the same way as the redhat box), it works
perfectly fine.
>>
>>Has anybody seen this type of error before, is i
Perrin Harkins wrote:
On Thu, 2004-07-22 at 11:26, MARTIN MOSS wrote:
This error doesn't occur on machines running the same code (mirrored
in the same way as the redhat box), it works perfectly fine.
Has anybody seen this type of error before, is it the symptom of some
other issue that I've missed
I'm not sure, is there a way to find out what options apache has been built with?
There are no differences in code & http.conf between the working machines, only OS versions.
MartyPerrin Harkins <[EMAIL PROTECTED]> wrote:
On Thu, 2004-07-22 at 11:26, MARTIN MOSS wrote:> This error doesn't occur
On Thu, 2004-07-22 at 12:06, MARTIN MOSS wrote:
> There are no differences in code & http.conf between the working
> machines, only OS versions.
Okay, if the code and conf are the same, and method handlers are enabled
as you told me off-list (don't do that), then I'm kind of at a loss. Is
it the
On Thu, 2004-07-22 at 11:26, MARTIN MOSS wrote:
> This error doesn't occur on machines running the same code (mirrored
> in the same way as the redhat box), it works perfectly fine.
>
> Has anybody seen this type of error before, is it the symptom of some
> other issue that I've missed somehow?
All,
I have a quirky issue concerning a redhat machine and Apache 1.
I have a method handler
sub handler ($$)
{
my $class=shift;
my $r = shift;
}
Which when running on a redhat linux machine dies with the error message "Attempt to bless into a reference" and when analysing the incoming v
12 matches
Mail list logo
