SYSTEM@CRNLNS.BITNET (08/05/87)
Derek and Anil, Thanks for your reminder about privileged user's files being created with the creator's uic rather than the directory owner's. As best I can tell, that is NOT what's going on. The two most recent files in question were written by a priv'd user in HIS OWN DIRECTORY. They appeared with the uic of a NON-PRIV'D account. Other files created in exactly the same way had the right owner. We have also seen this happen at random for completely non-priv'd people creating files in their own directories. There were no recorded disk errors or system crashes for the time the files were created. Now when people come to me complaining of their quota being out of whack (everybody knows about the extra blocks) I submit an overnight batch job that gets a complete directory of our entire user structure (3 ra81s) showing the owner fields of every file. I then have to go through all 90,000 files looking for ones with owners that don't agree with the owners of the containing directory. I usually find a dozen or so. grump grump Selden E. Ball, Jr. (Wilson Lab's network and system manager) Cornell University NYNEX: +1-607-255-0688 rLaboratory of Nuclear Studies BITNET: SYSTEM@CRNLNS Wilson Synchrotron Lab ARPA: SYSTEM%CRNLNS.BITNET@WISCVM.WISC.EDU Judd Falls & Dryden Road PHYSnet/HEPnet/SPAN: Ithaca, NY, USA 14853 LNS61::SYSTEM = 44283::SYSTEM (node 43.251)