Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!kth!enea!dkuug!freja!soren
From: soren@freja.diku.dk (J|rn Bo S|rensen)
Newsgroups: comp.os.misc
Subject: Re^2: Unix bigotry
Keywords: AOS AOS/VS ACL threads tasks processes
Message-ID: <4434@freja.diku.dk>
Date: 8 Feb 89 23:01:39 GMT
References: <1135@raspail.UUCP> <476@cvbnet2.UUCP> <653@unocss.UUCP> <117@spectra.COM>
Organization: DIKU, U of Copenhagen, DK
Lines: 17

pace@spectra.COM (William B. Pace) writes:

>               The bad part about ACL's was that you had to re-specify the
>ENTIRE access control list whenever you wanted to delete/change/add an entry
>(if you used the default CLI)....(Do they still do it this way?)

Yep! But a small 'shell-file' (CHACL <user/group>) could easily do it for you.

>but with a real nice extra.  Whenever a user accessed a file, the access
>was logged by account, number of accesses, date of last access and type
>of access.  Even if you PERMITted the file to the world, you could still
>get a list of the specific users that accessed the file.  

Just start SYSLOG/DETAIL=FULL (although that will quickly fill up your disks).
--------------------
Jan B. Andersen
aka :NET:MEZA.RUC.DK:UDD:D.JBA