[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
exetmp03 wrote: >> -----Original Message----- >> From: list-bounces@xxxxxxxxxxxxx >> [mailto:list-bounces@xxxxxxxxxxxxx] On Behalf Of Simon Williams >> Sent: 16 November 2006 13:35 >> To: list@xxxxxxxxxxxxx >> Subject: [LUG] Force permissions >> >> >> Hello everyone. >> >> I've been doing this with samba options for a while, but now >> that more >> people are logging directly into the server and/or using Linux it has >> become more of an issue. >> >> Quite simply, I've got a shared directory which everyone can use and >> write to. Through my research on this some time ago I found >> that I can >> set an 'inherit group' attrib by using SetGID on the dirs. >> >> Out of interest, what does setUID on a dir do? I've done some >> tests, but >> haven't noticed any difference. >> >> Anyway, if a user sets their umask to 002, it seems that all files >> become group writable, no matter what the permissions of the >> parent dir >> are. This isn't really desirable. >> >> So, what I'm looking for is some way of forcing the >> permissions of files >> created in the shared dir to be group writable. >> >> What is the conventional way of handling group write-ability >> for shared >> dirs? They can't seriously expect people to manually chmod >> all created >> files. >> >> I'm surprised google hasn't been very helpful on this one. Maybe I'm >> thinking about this all wrong. >> >> Thanks in advance > >> Simon > > If I remember right all permissions are set within the [share] > definition using umasks and that the Unix perms are irrelevant > > After that it should just work. It's all setup fine with samba. But what about people who are not using samba? e.g. direct shells (ssh) or nfs or ftp? -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html