On Sat, Nov 22, 2008 at 4:51 AM, Thomas Bächler <[EMAIL PROTECTED]> wrote: > Aaron Griffin schrieb: >> >> I'm confused. Does anyone know a better way to ensure g+w permissions >> when we do this stuff? How does git maintain permissions when the repo >> is set to shared? Would it be better to adjust the umask in the >> dbscripts? > > I say default ACLs! chmod the directory g+s and then run setfacl -m d:g::rwx > $DIR. This does not work when you mv files though, only when you cp or > create them (as mv does not modify the inode itself). > > umask might be another idea, not sure how this would work out, maybe it is > simpler. But you still need to cp instead of mv, as you would create the > temporary db file in a directory without the right group and setgid, so the > owning group would be the wrong one.
umask seems to work the way I want it to, so I'm going to work that code into it and remove the chmod stuff because it's all sorts of fail (still no idea why it works fine for me...)
