Xref: utzoo comp.unix.ultrix:922 comp.sys.dec:1266
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!helios.ee.lbl.gov!epb2!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.unix.ultrix,comp.sys.dec
Subject: group file permissions across NFS under Ultrix 3.0
Summary: workaround until DEC fixes it
Message-ID: <2644@helios.ee.lbl.gov>
Date: 14 May 89 16:52:21 GMT
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 33

Original problem:

>From article <2597@helios.ee.lbl.gov>, by envbvs@epb2.lbl.gov (Brian V. Smith):
>> remotely mounted file system.  In Ultrix 2.3 (and previous) the umask
> was used in determining the permissions when creating a file, but 
>> Ultrix 3.0 is ignoring it.
>> 

Here is a workaround provided by Jan Sanislo from washington.edu:

>I belive the problem stems from the fact that the default
>file creation mask (CMASK in sys/param.h) has been changed
>from 0 in 2.X to 022 in 3.0.  The nfs daemons (/etc/nfsd) on
>the server inherit this mask when they are started.  The
>protection modes of files created over the wire are &'d with
>~CMASK in the usual way.  It is thus impossible to enhance
>write permissions via a umask on the remote node (although
>it is possible to restrict them (e.g., umask 66).
>
>You should be able to cure the problem by saying "umask 0"
>before starting up /etc/nfsd in /etc/rc.local.  

This works. In other words:

(in /etc/rc.local)
	...
	umask 0
	/etc/nfsd 4
	...
_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
We don't need no signatures!