New files/directories having a specific group

Hi folks,

I've created a new Samba share where only 'mis' group members have
access, but when someone creates a new file, Samba assigns that user's
group as the owner. How can I get Samba to set 'mis' as the group
owner for all files or directories created in the share?

Thanks,

Alex

"Alex" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Hi folks,
>
> I've created a new Samba share where only 'mis' group members have
> access, but when someone creates a new file, Samba assigns that user's
> group as the owner. How can I get Samba to set 'mis' as the group
> owner for all files or directories created in the share?
>
[share name]

force group = mis

> Thanks,
>
> Alex

"m.marien" <mm(at)RiverCityCanada(dot)com> wrote in message news:<(E-Mail Removed)>...
> "Alex" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > Hi folks,
> >
> > I've created a new Samba share where only 'mis' group members have
> > access, but when someone creates a new file, Samba assigns that user's
> > group as the owner. How can I get Samba to set 'mis' as the group
> > owner for all files or directories created in the share?
> >
> [share name]
>
> force group = mis

Hello.

Thanks for the info Worked great.

Alex.

Alex wrote:

> Hi folks,
>
> I've created a new Samba share where only 'mis' group members have
> access, but when someone creates a new file, Samba assigns that user's
> group as the owner. How can I get Samba to set 'mis' as the group
> owner for all files or directories created in the share?
>
The unix way is to set the sticky group bit on the main directory of that
share (like drwxrwsr-x).

"Walter Mautner" <(E-Mail Removed)> wrote in message
news:23gs31-(E-Mail Removed)

> The unix way is to set the sticky group bit on the main directory of
> that share (like drwxrwsr-x).

sgid != sticky bit. This is a very common error that seems to arise from the
fact that the word sticky starts with an "s". The sticky bit has nothing to
do with the set group id permission.

The sgid perm you have indicated above is invoked via "chmod g+s dirname",
and assigns the same group id of the dirname to all files created below that
directory, and as such is the correct answer to the OP's question, but it is
*not* called "the sticky bit."

A "sticky bit" is denoted by a "t" in the world execute field of a directory
permission, and is granted by a chmod +t dirname. See the output of "ls -l /
/var | grep tmp" for an example. This assigns ownership of any file created
in that directory to the user who created the file.

The sticky bit on a parent directory allows only the owner of the file
within that directory, the owner of the parent directory or the superuser to
modify or delete the file.


tony

--
use hotmail com for any email replies



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

"ynotssor" <"ynotssor"> wrote:

> "Walter Mautner" <(E-Mail Removed)> wrote in message
> news:23gs31-(E-Mail Removed)
>
>> The unix way is to set the sticky group bit on the main directory of
>> that share (like drwxrwsr-x).
>
> sgid != sticky bit. This is a very common error that seems to arise
> from the fact that the word sticky starts with an "s". The sticky bit
> has nothing to do with the set group id permission.
>
Ah ... ok, just not native english speaker, I meant "sticky" is
applicable also for "group sticky" . Of course I know the "real"
sticky bit.
Thankx,
Greetings from Vienna