Path: utzoo!attcan!uunet!jarthur!nntp-server.caltech.edu!mustang!topgun!pprg.unm.edu!unmvax!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!wuarchive!emory!gatech!prism!msd!rhoward From: rhoward@msd.gatech.edu (Robert L. Howard) Newsgroups: comp.protocols.nfs Subject: Re: PC-NFS 3.0.1 net umask question. Message-ID: Date: 12 Oct 90 11:43:14 GMT References: <1990Oct12.003227.8315@amd.com> Sender: news@prism.gatech.EDU Organization: Georgia Tech Research Institute Lines: 40 In <1990Oct12.003227.8315@amd.com> indra@ashirvad.amd.com (Indra Singhal) writes: >In SunOS, a umask 022 would create directories with 755 permission and >all files with 644 permission. >In PC-NFS if you do a: net umask 022, even files are created with 755 >permissions which is not good. And if you try using 'net umaks 133' any >directories you make are unusable. >Has anyone noticed this? Yes. > Am I doing something wrong? Nope. There is nothing you can do (wrt getting the umask to work as under SunOS). I *hope* this will be fixed in the next release of PC-NFS (hint, hint). What we do is set the umask to 133 (or 113, etc.) and then have a batch file to make directories on the network drives. All you need is... ---------------nmd.bat--------------- @echo off mkdir %1 chmod a+x %1 ------------------------------------- >Email please. Thanks. I think (hope) this is general interest enough to be posted. Robert -- | Robert L. Howard | Georgia Tech Research Institute | | rhoward@msd.gatech.edu | MATD Laboratory | | (404) 528-7165 | Atlanta, Georgia 30332 | | UUCP: ...!{allegra,amd,hplabs,ut-ngp}!gatech!msd!rhoward |