comp.os.linux.networking

On Mar 7, 7:02=A0am, Ken Teague <"kteague at pobox dot com"> wrote:
> We've got a NetApp filer that is exporting NFS and CIFS and the PC's
> that are accessing them are Windows and Linux systems. =A0When a user on a=

> Linux system creates a new file or directory, the umask is 002 and, as
> such, it's not accessible from a Windows box due to the permissions that
> are set on it.

I don't follow that. I've just tried it at work and it's fine.

I'm a little puzzled as what you're after seems to be a umask that
turns off more permissions than the current setup so I don't yet
understand why the file would be inaccessible for the more lax case.


> Also, if we
> forget to set that, it could lead to a lot of files being owned by an
> improper user:group and would be more of a pain to fix the problem it
> created.

Where would this "improper" user:group would come from?

Is it the same user name accessing via CIFS and NFS? (Or at least a
CIFS user name mapped to the local user).

Paul