Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14036 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92062 invoked by uid 1010); 9 Dec 2004 17:25:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 92009 invoked from network); 9 Dec 2004 17:25:12 -0000 Received: from unknown (HELO stack.fission.org.uk) (195.82.120.217) by pb1.pair.com with SMTP; 9 Dec 2004 17:25:12 -0000 Received: from bassman.fission.org.uk ([82.70.115.109]) by stack.fission.org.uk with esmtp (Exim 3.36 #1 (Debian)) id 1CcS22-0002vE-00 for ; Thu, 09 Dec 2004 17:24:46 +0000 Received: from 127.0.0.1 (AVG SMTP 7.0.289 [265.4.8]); Thu, 09 Dec 2004 17:24:56 +0000 Message-ID: <41B88A68.4080506@fission.org.uk> Date: Thu, 09 Dec 2004 17:24:56 +0000 User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: default directory/file modes From: gareth@fission.org.uk (Gareth Ardron) Guys, Been all through the documentation on this one and it's doing my head in a bit. I can't find any way to specify a default directory mask to use for file and/or directory creation at all. Now, if I'm just being blind, can somebody help me out - otherwise, I'd like to propose this as an addition. I'm happy to code it up myself if nobody else wants to do it and if it's ok to put it in. It would require an ini entry however (I know, I know) and I can't see how it'd work outside of a *nix environment as well - those points aside, it'd be really really useful. Oh, and another one I'd like to propose (but don't know enough about webservers internals to code myself) is like we have can php_value in apache configs on a per-virtualhost directive, we can't currently specify extensions to use on per-virtualhost directive which is kinda irritating. I've got several users I trust, and several I don't. I'd rather limit what those few can do by knocking out extensions for their virtualhosts if at all possible - or more accuratly, explicitly enabling extensions for users I do trust. Cheers, -- Gareth Ardron