Jeff Boes wrote:
Stas Bekman wrote:
Jeff Boes wrote:
We moved our webserver from a machine where mod_perl was built under
Perl 5.6.1, to a server where it was built under 5.8.1. Now, Perl
scripts run but produce no browser output!
open(STDOUT,'>- :stdio') or die $!;
This code runs, and prod
Stas Bekman wrote:
Jeff Boes wrote:
We moved our webserver from a machine where mod_perl was built under
Perl 5.6.1, to a server where it was built under 5.8.1. Now, Perl
scripts run but produce no browser output!
open(STDOUT,'>- :stdio') or die $!;
This code runs, and produces output in th
Jeff Boes wrote:
We moved our webserver from a machine where mod_perl was built under
Perl 5.6.1, to a server where it was built under 5.8.1. Now, Perl
scripts run but produce no browser output!
For example:
begin code-
#! /usr/bin/perl -w
open (TMP,">/tmp/hello.log") or die
Stas Bekman wrote:
Here is how I normally do that, YMMV. It's pretty clear that I didn't
write the message below ;) You may want to strip the CC and other
headers...
Original Message
Subject: Re: [Fwd: Re: [Fwd: Apache::AuthenSmb]]
Date: Wed, 15 Oct 2003 11:24:46 -0500
From: s
Brian McCauley wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
[...] this is your document so I shall go along with your preferences.
It's not really mine, I just happen to maintain it. From the previous
discussion it seems that those who cared agreed that it's better to
explicitly declare var
We moved our webserver from a machine where mod_perl was built under
Perl 5.6.1, to a server where it was built under 5.8.1. Now, Perl
scripts run but produce no browser output!
For example:
begin code-
#! /usr/bin/perl -w
open (TMP,">/tmp/hello.log") or die $!;
print TMP "S
Perrin Harkins wrote:
On Wed, 2003-10-15 at 15:13, Stas Bekman wrote:
The biggest problem with Apache::compat is that it modifies the behavior of
several methods to behave like they did in mp1. So if you run on the same
server some code that relies on their mp2 behavior, there is a conlict.
Th
On Wed, 2003-10-15 at 15:13, Stas Bekman wrote:
> The biggest problem with Apache::compat is that it modifies the behavior of
> several methods to behave like they did in mp1. So if you run on the same
> server some code that relies on their mp2 behavior, there is a conlict.
That makes sense. S
Perrin Harkins wrote:
I recently gave some advice on perlmonks.org to a person who was
concerned about what his migration path would be if he develops for
mod_perl 1 right now. I told him he will be safe if he uses
Apache::Registry, since he should be able to run his A::R scripts under
ModPerl::Re
Ronald Beck wrote:
In UNIX, there's also something called a .forward file which can contain
an email address to send to. For example, if John had an account on
SysA but he wanted his email to go to SysB, he would create a .forward
file in his home directory that would contain the following...
[EM
I recently gave some advice on perlmonks.org to a person who was
concerned about what his migration path would be if he develops for
mod_perl 1 right now. I told him he will be safe if he uses
Apache::Registry, since he should be able to run his A::R scripts under
ModPerl::Registry unchanged (assu
In UNIX, there's also something called a .forward file which can contain
an email address to send to. For example, if John had an account on
SysA but he wanted his email to go to SysB, he would create a .forward
file in his home directory that would contain the following...
[EMAIL PROTECT
Stas Bekman <[EMAIL PROTECTED]> writes:
> Brian McCauley wrote:
> > Stas Bekman <[EMAIL PROTECTED]> writes:
> >
> >>- move the perl4 lib solution to the perl_reference.pod
> > Will do when I get round to that bit. I still think a mention of it
> > is needed in porting.pod to warn people away from
Here is how I normally do that, YMMV. It's pretty clear that I didn't write
the message below ;) You may want to strip the CC and other headers...
Original Message
Subject: Re: [Fwd: Re: [Fwd: Apache::AuthenSmb]]
Date: Wed, 15 Oct 2003 11:24:46 -0500
From: speeves <[EMAIL PROTEC
Ged Haywood wrote:
Hello again,
On Wed, 15 Oct 2003, speeves wrote:
BTW, how are we dealing with forwards again? (Do I just send them
forward, or just copy on the reply?)
I'm not sure I fully understand the question, but I don't think it
really matters as long as things are clear. If
Hello again,
On Wed, 15 Oct 2003, speeves wrote:
> BTW, how are we dealing with forwards again? (Do I just send them
> forward, or just copy on the reply?)
I'm not sure I fully understand the question, but I don't think it
really matters as long as things are clear. If when you forward mail
y
Hi there,
On Wed, 15 Oct 2003, speeves wrote:
> I've installed AuthenSmb and Authen::Smb to a freshly compiled version of 5.8.1 and
> when I use the module in Apache (1.3.28) with mod_perl 1.29, I get an error in the
> error_log file as follows:
>
> [error] Can't locate object method "get_basi
Hi there
I've installed AuthenSmb and Authen::Smb to a freshly compiled version of 5.8.1 and when I use the module in Apache (1.3.28) with mod_perl 1.29, I get an error in the error_log file as follows:
[error] Can't locate object method "get_basic_auth_pw" via package "Apache" at /usr/local/lib/
--- Stas Bekman <[EMAIL PROTECTED]> wrote: > Sreeji K
> Could it be that you were going through some proxy,
> and either the server has
> failed to give proper headers or the proxy is
> broken?
Yes I was using a proxy. However, I don't think it
was a proxy error, as I had downloaded a couple of
Sreeji K Das wrote:
--- Stas Bekman <[EMAIL PROTECTED]> wrote: > Sreeji K >
When did you do that? I have just tested and it
fetches 1.29. Could it be that
you had an older file laying around?
hmm.. looks like that. I used lynx to download the
file & the directory had an old file. I don't know why
--- Stas Bekman <[EMAIL PROTECTED]> wrote: > Sreeji K >
When did you do that? I have just tested and it
> fetches 1.29. Could it be that
> you had an older file laying around?
hmm.. looks like that. I used lynx to download the
file & the directory had an old file. I don't know why
lynx never gave
21 matches
Mail list logo