I can't seem to find this in the books or online docs
All files seem to be created 600 owned by the Apache user/group - which
is a little annoying for me
is there a setting available?
Doesn't that depend on the umask set for the user?
Tom
jonathan vanasco wrote:
I can't seem to find this in the books or online docs
All files seem to be created 600 owned by the Apache user/group - which
is a little annoying for me
is there a setting available?
It should -- but a lot of other 'environments' / 'frameworks' have
"ideal" ways to set it.
for instance the Exim MTA will let you hardcode it into the binary as
a global value, or set it in certain places for different behavior
I'm wondering if mod_perl has a similar mechanism
On Mar 7, 2
jonathan vanasco wrote:
I can't seem to find this in the books or online docs
All files seem to be created 600 owned by the Apache user/group - which
is a little annoying for me
is there a setting available?
Could you please be more specific, jonathan? What 'all files' are you
talking about?
mo
This was in reference to :
case a)
open FILE , ">/path/to/file";
print FILE "";
close FILE;
case b)
$upload = $apr->upload("identifier");
$upload->link("/path/to/file");
I'm sure there are other cases, such as
In any event:
files are created oct(600)
directories are
jonathan vanasco wrote:
This was in reference to :
case a)
open FILE , ">/path/to/file";
[...]
right now i just umask before the file creation each time, and that
works, but like everyone else here, i want what works best
I see. In which case it has nothing to do in particular with modperl. It
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
After posting on the libaprq list i learned this:
"libaprq has the file permissions hardcoded to 0600 and ignores the
user's umask"
chmod is in order.
On Mar 18, 2005, at 12:20 AM, jonathan vanasco wrote:
Just setting a simple umask did do the trick for 90% of my needs
I'm stuck on one issue th
