dbfunk@ICAEN.UIOWA.EDU (David B Funk) (07/08/89)
How do I make the sr10 "install" tool respect my initial default ACLs? I have "closed" systems with "Aegis" style ACLs for the system directories (such as /sys & /lib). Entries in the "baseline" file are: Set acl closed Set never_asked1 N/A Set acl_style aegis I have some optional products that I now want to install, such as gmr3d & phigs. I went thru the sequence of cfgsa, config, and install. When I got done, the ACLs on the new files had nothing to do with the inital default ACLs on their directories. Here are the ACLs that I have for "/lib": $ acl /lib -all Acl for /lib: Required entries root.%.% prwx- %.sys_admin.% prwxk %.%.none [ignored] %.%.% -r-x- Extended entry rights mask: ----- Initial (default) acl for directories created under /lib Required entries For the current process: root.%.% prwx- %.sys_admin.% prwxk %.%.none [ignored] %.%.% -r-x- Extended entry rights mask: ----- Initial (default) acl for files created under /lib Required entries For the current process: root.%.% prwx- %.sys_admin.% pr-xk %.%.none [ignored] %.%.% -r-x- Extended entry rights mask: ----- Here is the ACL on "phigslib" after install put it in /lib: $ acl /lib/phigslib Acl for /lib/phigslib: Required entries root.%.% prwx- %.staff.% prwx- %.%.none prwx- %.%.% prwx- Extended entry rights mask: ----- Is this a bug or a "feature"? Dave Funk