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 ucbvax.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!decwrl!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: File Ownership
Message-ID: <9378@ucbvax.ARPA>
Date: Fri, 26-Jul-85 20:33:01 EDT
Article-I.D.: ucbvax.9378
Posted: Fri Jul 26 20:33:01 1985
Date-Received: Sun, 28-Jul-85 09:27:35 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 23

From: zar%xhmeia@cit-hamlet.arpa

I'm using VMS V4.1 now and me being the crazy system manager that I am
go helping others by using privs to consult with a user on a problem in
their personal directory without using their account to relogin (all with
permission, of course). Under VMS V1-3 when a user created a file, the
file was owned by the UIC of the person who created the file. Lately,
when I DIRECTORY/OWNER to clean up files I've created in someone elses
directory, all the files are owned by the UIC of the owner of the direc-
tory containing the new files. For example,
	$ SET DEF [SAM]
	$ CREATE X.X
	$ DIRECTORY/OWNER
will show the owner as the owner of the directory [SAM] regardless of
who actually created the file X.X. I noticed, though, this can be changed
by typing SET FILE/OWNER=[newuic] X.X. This is definitely not how VMS/RMS
should work in my opinion. Has anyone else seen this, or can anyone
confirm this (am I hallucinating???)?

						From The Great
						     Zar
						a.k.a. Dan Zirin
						ZAR%XHMEIA@CIT-HAMLET