Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Ownership problems?
Message-ID: <4e0b16e4.1bc5b@pisa.ifs.umich.edu>
Date: 16 Nov 90 16:02:06 GMT
References: <1990Nov15.220419.20222@nntp-server.caltech.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 24

In article <1990Nov15.220419.20222@nntp-server.caltech.edu>, mughal@iago.caltech.edu (Mughal, Asim) writes:

  We have Apollo DN4500 showing some of the files in /user as following;
  
  (eg)
  -rwxrwxrwx+   1 -1        543 Aug 7 1990 esmsim.prm*
  
  and other files as ;
  
  -rwxrwxrwx+   1 none      213 Aug 7 1990 ps*   
  
  etc etc.

The '+' at the end of the mode indicates that this file has a non-Unix acl
attached to it.  "Ownership" doesn't necessarily mean what you think it does
for these files.

If you don't understand and don't want acls, you could go through all your
directories and files and get rid of the acls.  You can do this with 'chacl
-B'.  Warning: you can screw yourself up this way, too, if there was some
reason for a strange acl being attached to a file.  Only do this on user
files, not system files, unless you know what you're doing.

Read the 'acl' man page for more details.