NFS file modes consistency among different operating systems

[Mehmet Erol Sanliturk]

On Mon, Sep 16, 2013 at 11:53 PM, aurfalien <aurfalien at gmail.com> wrote:

> From your non MS$ clients, open a shell and type umask, what returns?
>
> Sounds like your default umask needs changing is all.
>
> I would suggest going with a umask of 775 and ensuring all ppl requiring
> mod access be group members of what you have settled on.
>
>
>
> - aurf
>
> On Sep 16, 2013, at 8:41 PM, Mehmet Erol Sanliturk wrote:
>
> > Dear All ,
> >
> >
> > I have NFS 3 in FreeBSD 9.1 amd64 .
> >
> > The clients are FreeBSD , Linux , Windows XP through Samba on the same
> > files .
> >
> > The Windows XP is able to access , use and modify files created or
> modified
> > by any other operating system user .
> >
> > In contrary , FreeBSD and Linux users are NOT able to such sharing
> because
> > files are created by another user and access mode settings are not
> > changeable due to owner of files .
> >
> > It is very likely that some settings are missing but I do not know which
> > ones .
> >
> > One remedy is to use NFS server in root logged state and change file
> modes
> > frequently  ( An ordinary user in server is NOT permitted to change modes
> > of files created by other users although exported directories owned by
> such
> > a user ) .
> >
> > How can I solve the following problem :
> >
> > No any client should be able to change file modes set in server
> > All files created by client should inherit modes set in server directory
> .
> >
> >
>


Linux umask : 0002
FreeBSD umask : 0022


Changing client umask to 775 is not solving the problem , because in NFS
server , they are setting their own modes without considering existing
umask .

When a file is modified by a user , the other users in FreeBSD and Linux
are not able to access to these files even their umask values are 775 .

The Linux user is defined in groups 1000 and 1001 but this is also not
permitting access to files modified by other users whether their group is
1000 or 1001 .





> > Thank you very much .
> >
> > Mehmet Erol Sanliturk
> >
>