Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site lzwi.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!lzwi!nrh From: nrh@lzwi.UUCP (N.R.HASLOCK) Newsgroups: net.decus Subject: Re: set protection Message-ID: <254@lzwi.UUCP> Date: Wed, 21-Aug-85 10:33:24 EDT Article-I.D.: lzwi.254 Posted: Wed Aug 21 10:33:24 1985 Date-Received: Sat, 24-Aug-85 13:26:23 EDT References: <696@gatech.UUCP>, <18300002@inmet.UUCP> <993@sphinx.UChicago.UUCP> Organization: AT&T Information Systems, Lincroft Lines: 22 Summary: /def In article <993@sphinx.UChicago.UUCP>, pwyc@sphinx.UChicago.UUCP (Peter Chen) writes: > 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? > - Peter Chen Two choices. Set Prot (....)/def defines the default protection for all subsequently created files. Alternatively, Create a logout.com file which does the specific set prot of .dat files. You may need to point logout at the file. i.e. lo*gout := @logout.com -- -- {ihnp4|vax135|allegra}!lznv!nrh Nigel The Mad Englishman or The Madly Maundering Mumbler in the Wildernesses Everything you have read here is a figment of your imagination. Noone else in the universe currently subscribes to these opinions. "Its the rope, you know. You can't get it, you know."