Sun, 04 Oct 2026 04:37:48 +0200 http://www.polarhome.com/horde/whups/ticket/?id=14 creating new file seems to ignore the directory's ACL When a new file is created in VMS (e.g. using CREATE, or by FTP-putting the file), the access rights are set based on 1) the default process protection (the "umask") - see SHOW PROT, 2) the directory's ACL the latter taking precedence. It seems that vim does not do step 2, i.e. it does not consult the directory's ACL, and only checks the umask. As a result, files freshly created using vim may have different protection settings than files created with other editors. Example: $ set prot=w /default $ sh prot SYSTEM=RWED, OWNER=RWED, GROUP=RE, WORLD=NO ACCESS $ cre/dir [.abc] $ set secu []abc.dir /delete=all/acl=(default_protection,s:rwed,o:rwed,g:r,w:r) $ dir/acl abc.dir ... ABC.DIR;1 (DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RWED,GROUP:RE,WORLD:RE) ... $ set def [.abc] $ create novim.txt [ctrl-z to end input] $ vim vim.txt [:wq in vim] $ dir/prot ... NOVIM.TXT;1 (RWED,RWED,RE,RE) VIM.TXT;1 (RWD,RWD,R,) ... As seen, the files have different protection rights set up: - NOVIM.TXT is world-readable, because it respects the default ACLs of ABC.DIR - VIM.TXT is world-unreadable, because vim only consulted the default protection (as seen in SHOW PROT) I guess this is not correct. Thu, 20 Feb 2014 11:55:00 +0100 http://www.polarhome.com/horde/whups/ticket/?id=14#t28