From: Adam R. <ad...@ex...> - 2011-10-18 13:14:53
|
Okay, but am I correct in thinking that umask is applied per user? i.e. it lives in the users profile? It is the mount point of the fs that defines the overarching degfault permissions right? The way 'default permissions' in eXist-db were implemented previously were neither per user or per mount. I think permission inheritance with ACL will render umask unneeded? On 18 October 2011 12:22, Hungerburg <pc...@my...> wrote: > Am 2011-10-18 13:08, schrieb Adam Retter: >> This is an interesting argument and one that I am not deaf to. However I >> would like to know if there is a known mechanism in Unix for this? > > The *nix mechanism is called "umask": it specifies the permissions that > will be subtracted from the default/full, ie rw-rw-rw on files and > rwxrwxrwx on directories, permissions. Its a per process setting that > will be passed on to forked children. > > From wikipedia: "The addition of umask (in around 1978) allowed sites, > groups, and individuals to chose their own defaults. Small close groups > might choose 000, computer centers 022, security-conscious groups 077 or > 066 for access to sub-directories under private directories." > > -- > peter > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |