Newsgroups: comp.protocols.nfs
Path: utzoo!utgpu!cunews!micor!latour!ottsun1!pickles
From: pickles@mpr.ca (Clive Pickles)
Subject: PCNFS, permissions, and UMASK
Message-ID: <1991Apr3.195733.15063@ottsun1.uucp>
Keywords:  PC-NFS, UMASK, permissions
Sender: pickles@ottsun1.uucp (Clive Pickles)
Organization: MPR Teltech Ltd., Ottawa, ON, Canada
Distribution: na
Date: Wed, 3 Apr 91 19:57:33 GMT

This has probably been asked before (Ha!  What hasn't?! :-) but if it has,
I haven't seen anything about it.  Here is my problem:

I have created a file using PCNFS with permissions 770.  I would like people
in my group to be able to update this file.  However, when they do the
update, the permissions of the updated file are set to whatever the UMASK
is of the updater.  Most people have a UMASK of 027, so whenever they update
one of my files, the permissions are set to 750.  Because the owner of the
file is also changed, I now cannot edit that file.

This is different than Unix, which keeps the original file permissions and
owner until they are explicitly changed with chmod and chown.

I know that I could ask my users to do a "chmod" on the file after editing
it, but most people are running in a menu-shell environment, and do not
normally exit the "safe" environment of the menu.

I know WHY this happens (DOS copies the old file and renames the new one),
but I think that PC-NFS should be able to account for this.  We are running
PCNFS 3.0.1.  My questions is:  anybody know if this is changed for release
3.5?  Thanks to anyone who gives me an answer. 

-- 
===================================================================
= Clive Pickles - Systems Administrator MPR Teltech Ltd. (Ottawa) =
= Phone: (613) 787-4159 ------------------ E-mail: pickles@mpr.ca =
===================================================================