Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!haven!decuac!grebyn!media!rmf
From: rmf@media.uucp (Roger Fujii)
Newsgroups: comp.protocols.nfs
Subject: Re: Why does NFS suppress group-write permission?
Message-ID: <1990Jul11.043004.15349@media.uucp>
Date: 11 Jul 90 04:30:04 GMT
References: <417@minya.UUCP> <3619@auspex.auspex.com>
Organization: Media Cybernetics, Inc.
Lines: 15

guy@auspex.auspex.com (Guy Harris) writes:
>Now, checking the S5R3 source reveals that its file system code *does*
>use the umask - i.e., umasking isn't done at the system call level, it's
>done at the file system level.  (I expect this to be fixed in S5R4,
>given that S5R4 uses the same general sort of VFS mechanism as SunOS 4.x
>and NFSSRC4.0.)  So it's conceivable that in an NFS implementation under
>an S5R3-derived system, an "nfsd" with a umask of 022 could gratuitously
>turn off group write permission.

It is also subject to ***NASTY*** things like ulimit.... ISC's sys5.3
has this problem.  Really nasty.  Motto:  make sure nfsd inherits
the correct environment values.
-- 
Roger Fujii - Media Cybernetics		Phone: (301)495-3305
Internet: rmf%media@uunet.uu.net 	UUCP: {uunet,hqda-ai}!media!rmf