comp.os.linux.networking

Paul Black wrote:
> I'm guessing (since I don't have NIS on my machine) that that would
> set the umask for the NIS files only.

Gah! That's not what I want. :-( Maybe I should elaborate on my
problem in more detail.

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. When 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.

Previously, all of these files were on a Linux box running Samba, and
they were owned by, say, userX:userX, and the permissions were set to
rwx for user and group (umask 022). Just to make things easy (and the
same as before), we'd like to make the default umask 022, and this
includes any new Linux boxes that are introduced into the environment.
Of course, setting this on each and every box is a pain. 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.

What is an elegant way to ensure all hosts (current and new) have a
default umask of 022?


>> If so, is there anything else I can do to prevent the override?
>
> If you mean preventing a user from setting their own umask? Probably
> not.

I was aiming more toward a local config file on the host PC overriding
what we may be able to set the umask to via NIS (hope that makes sense
:-). Again, using the "I forgot to modify the umask on this new PC"
scenario.

Thanks for the input, Paul.

- Ken