Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site bunny.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!bunny!epm0 From: epm0@bunny.UUCP (Erik Mintz) Newsgroups: net.decus Subject: Re: The Great Net Cleanup Part IIa (File protection) Message-ID: <167@bunny.UUCP> Date: Mon, 19-Aug-85 23:49:33 EDT Article-I.D.: bunny.167 Posted: Mon Aug 19 23:49:33 1985 Date-Received: Sat, 24-Aug-85 01:08:00 EDT References: <696@gatech.UUCP>, <18300002@inmet.UUCP> <993@sphinx.UChicago.UUCP> Organization: GTE Laboratories, Waltham, MA Lines: 38 > I want to make all my data files readable to the world (in VMS), so I do a > SET PROTECTION (W:R) *.DAT;* (don't have the manual in front of me, so I > could be off on the syntax), and it works fine; but the protection seems > to apply only to .DAT files existing at the time the command is executed. > Newer files, even newer versions of existing files, seem to lose this > protection. Does anyone know how to circumvent this problem? You are correct about the protection applying to existing files only. There are two options that you can use to fix this problem. 1) SET PROTECTION=W:R/DEFAULT This will cause ANY file you create to be world readable. (put this in your LOGIN.COM) 2) Use the ACL facility of V4.x I am sure that this will allow you to fix the later version problem, but I don't think it will help the new file problem. Another alternative (unclean) is to do something like LOGO*UT == "@sys$login:logout.com" ! (do this in your LOGIN.COM) and have logout.com (in your login directory) execute SET FILE/PROT=W:R *.dat;* This will reset your protection each time you log out, and will in fact work arround the problem. On the other hand, it will go and reset the protection on each file every time you log off, regardless of whether the file is new or not. -- Erik Mintz ARPA or CSnet : epm0%gte-labs.csnet@csnet-relay UUCP: ...harvard!bunny!epm0