On Wednesday 23 May 2007 14:49, Joachim Schrod wrote: > Phil answered your question how to enable the RH behavior by > setting the umask globally. > > If you don't want to do this, there is the possibility to use > access control lists (ACLs); the default ACL determines the access > right of newly created files. > > I don't know if the global umask setting is sufficient for you, so > I stop here with the explanation; ask, if you need more info. > > But note: both methods don't support changing the access rights of > files that are created elsewhere, e.g., in a personal directory, > and moved to the shared directory. (That's because moving doesn't > create a file, it just changes the directory entry. (Reality is > even more complex, but hopefully you'll see what I mean.))
Hi Joachim, Do you know where I can set the umask globally in Suse? However, I don't think setting up the umask globally would be "as safe as" in RH, because Suse doesn't use the concept of UPG (user private group). So, if I set the umask globally, then it means every user can access those files and directory in the "test" directory. You mean ACL as in "extended ACL" from setfacl? I think I can try "create" the UPG situation like in RH, but it means I have to "remove" all related users from the 'user' group. Not practical. Or, after some browsing on /etc/apparmor directory, I think it's possible to set the umask for the 'test' directory and files. I'm not sure. -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 6:00pm up 9:53, 2.6.18.2-34-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
pgpbhDvG2Qf00.pgp
Description: PGP signature
