Just setting a simple umask did do the trick for 90% of my needs
I'm stuck on one issue though --
$req = Apache::Request->new($r);
$upload = $req->upload("foo");
$upload->link('/path/to/file');
no matter what or when I set the umask, file permissions are unix 600
I say 'when', because
Nick *** wrote:
[...]
But there is another bug as I said.
Just run perl Makefile.PL MP_STATIC_EXTS=1 MP_COMPAT_1X=0 MP_USE_STATIC=1
MP_AP_CONFIGURE="--with-mpm=prefork" MP_AP_PREFIX=/usr/src/httpd
and then run make. You will see what happens :)
Indeed, I can reproduce it. Here is a quick bandaid (
Malcolm J Harwood <[EMAIL PROTECTED]> writes:
> On Wednesday 16 March 2005 11:12 pm, Joe Schaefer wrote:
[...]
>> The RFC is a guideline, not the final arbiter. This link is exactly
>> what you are looking for:
>
>> http://apr.apache.org/docs/apr-util/group___a_p_r___util___date.html#ga1
>
> Ex
On Wednesday 16 March 2005 11:12 pm, Joe Schaefer wrote:
> > How about simply correcting the parse_http docs from:
> > The date string can be in one of the following formats:
> > to:
> > The date string can be in one of the following formats (as per RFC2616):
> >
> > That way anyone intere
James Orr wrote:
Hi,
I have an occaisional error happening with a module i'm using from a
mod_perl script. This is in my "new" method ...
my $ifh = IO::File->new($project_dir.'/info.xml') || die "Can't open
info file: $!";
$data->{'info'} = $parser->parse_fh($ifh);
And the error it gives is ...
re
Stas Bekman wrote:
> John Siracusa wrote:
>
>> Looking at $ENV{'MOD_PERL'} is mostly fine with me, but it does bother me
>> that I have to strip out the version using a regex and then compare it to
>> 1.99. (What if the format of that string changes someday?)
>> $ENV{'MOD_PERL_API_VERSION'} wil
Andrew Green wrote:
Hi,
I'm encountering an occasional error with a couple of Apache::Registry
scripts, exemplified thus:
Can't locate object method "handler" via package "handler"
(perhaps you forgot to load "handler"?) at
/path/to/my/registry/program line 12.
[...]
Most
John Siracusa wrote:
Looking at $ENV{'MOD_PERL'} is mostly fine with me, but it does bother me
that I have to strip out the version using a regex and then compare it to
1.99. (What if the format of that string changes someday?)
$ENV{'MOD_PERL_API_VERSION'} will help there, I think.
As of this mome
On Thu, 2005-03-17 at 21:08 +0100, Clinton Gormley wrote:
> Doing a search, though, I found a discussion that Perrin had commented
> on in 2003, not recommending its usage in any environment, never mind
> mod_perl.
>
> http://aspn.activestate.com/ASPN/Mail/Message/modperl/1925101
>
> Is this stil
> Looking at $ENV{'MOD_PERL'} is mostly fine with me, but it does bother me
> that I have to strip out the version using a regex and then compare it to
> 1.99. (What if the format of that string changes someday?)
yes, exactly. we just had this same conversation on dev@ last week :)
> $ENV{'MOD
On Thu, 17 Mar 2005 14:57:24, Geoffrey Young <[EMAIL PROTECTED]>
wrote:
> just added to svn is $ENV{MOD_PERL_API_VERSION}, which is currently just "2".
Cool.
> what exactly is the issue you guys are trying to work around?
I'm writing code that's intended to work under both MP1 and MP2. To split
Hi all
It's good to be back on this list - been a while :)
Recently, I've used Error.pm for a few projects and I love the interface
- makes coding a whole lot simpler.
Doing a search, though, I found a discussion that Perrin had commented
on in 2003, not recommending its usage in any environment
John Siracusa wrote:
> On Thu, 17 Mar 2005 17:39:21, Dominique Quatravaux <[EMAIL PROTECTED]> wrote:
>
>>For the record I use the following dubious hack as an interim measure:
>>
>>sub modperl_major_version {
>>~use DynaLoader ();
>>~return 1 if DynaLoader::dl_find_symbol_anywhere("XS_Ap
On Thu, 17 Mar 2005 17:39:21, Dominique Quatravaux <[EMAIL PROTECTED]> wrote:
> For the record I use the following dubious hack as an interim measure:
>
> sub modperl_major_version {
> ~use DynaLoader ();
> ~return 1 if DynaLoader::dl_find_symbol_anywhere("XS_Apache_define");
> ~return
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have a few places in my code where I clobber %ENV for various
reasons (mostly taint-safety). The problem is that I can no longer use
$ENV{MOD_PERL} to detect whether I'm running under mod_perl or not.
And to be frank, I don't think detecting an
Hi,
I'm encountering an occasional error with a couple of Apache::Registry
scripts, exemplified thus:
Can't locate object method "handler" via package "handler"
(perhaps you forgot to load "handler"?) at
/path/to/my/registry/program line 12.
Here's the program up to and
Hi,
I have an occaisional error happening with a module i'm using from a
mod_perl script. This is in my "new" method ...
my $ifh = IO::File->new($project_dir.'/info.xml') || die "Can't open
info file: $!";
$data->{'info'} = $parser->parse_fh($ifh);
And the error it gives is ...
read on filehan
>Nick *** wrote:
>> As I wrote in a previous mail, there is another error with the
>> MP_STATIC_EXTS=1 option. When running make, the process dies with:
>>
>> cp Base64.pm ../../../blib/lib/APR/Base64.pm
>> make[3]: *** No rule to make target
>> `../../../blib/arch/auto/APR/Base64/Base64.
18 matches
Mail list logo
