Re: [SMARTY-DEV] setting up directories
| From: | messju mohr | Date: | Wed, 20 Aug 2003 11:39:05 +0000 |
| Subject: | Re: [SMARTY-DEV] setting up directories | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-1779@lists.php.net to get a copy of this message | ||
On Wed, Aug 20, 2003 at 02:12:55PM +0400, Konstantin A. Pelepelin wrote:
> On Tue, 19 Aug 2003 15:30:48 +0200, Messju Mohr <messju@lammfellpuschen.de>
> wrote:
>
>
> >chown [webserver_user].[ftp_user's_group]
> >chmod 770 templates_c
> >chmod g+s templates_c
> >
> >[and in php:]
> >umask(0007);
> >$smarty->_file_perms = 0660;
> >$smarty->_dir_perms = 0770;
> >
> >
> >this makes the files created owned by the webserver-users (so he has
> >full permissions), but due to the group-sticky-bit of the directory
> >the files' group is your ftp-user's group. so the ftp-user has write
> >permissions via the group-writable flag.
>
> Doesn't it worth noting this case in documentation?
>
> 'chmod' man page says nothing about meaning of SGID-bit on directories, and
> it may work or may not work on some OSes or filesystems. On Linux 2.4
> ext2(3)fs it works as you say.
yes, i should have mentionend that this works for me and was tested
only on a linux-box. AFAIR i found this out by trial-and-error ages
ago and never bothered to verify the documentation why and where it
worked.
if we can draw a clear line which systems support this and which may
not it may be worth a technical note in the docs, IMHO.
> WBR,
> Konstantin A. Pelepelin