[3819] in Athena Bugs
vax 6.4R: libacl.a
daemon@ATHENA.MIT.EDU (Ezra Peisach)
Wed Dec 13 12:55:09 1989
To: bugs@ATHENA.MIT.EDU
Date: Wed, 13 Dec 89 12:54:42 EST
From: Ezra Peisach <epeisach@ATHENA.MIT.EDU>
------- Forwarded Message
Received: by E40-PO.MIT.EDU (5.45/4.7) id AA02920; Wed, 13 Dec 89 11:09:29 EST
Received: from LYCUS.MIT.EDU by ATHENA.MIT.EDU with SMTP
id AA02651; Wed, 13 Dec 89 11:09:22 EST
Received: by lycus.MIT.EDU (5.61/4.7) id AA00878; Wed, 13 Dec 89 11:09:19 -0500
Date: Wed, 13 Dec 89 11:09:19 -0500
From: John T Kohl <jtkohl@ATHENA.MIT.EDU>
Message-Id: <8912131609.AA00878@lycus.MIT.EDU>
To: testers@ATHENA.MIT.EDU
Subject: vax 6.4R: libacl.a
X-Us-Snail: MIT Room E40-351, 1 Amherst St., Cambridge, MA 02139 USA
System name: lycus
Type and version: CVAXSTAR 6.4R
Display type: SM
What were you trying to do?
Update an ACL file by snapping its symbolic link and editing a
new file.
What's wrong:
libacl.a doesn't notice when a file changes if it was a symlink.
I edited an acl by snapping a symlink to it, and creating a new
file. The access routines didn't notice the change.
What should have happened:
It should have noticed that the file had changed completely. I
suspect the same thing will happen if a file is renamed and recreated.
It does the Right Thing if a file is modified in place.
Please describe any relevant documentation references:
it's missing, see next report
------- End of Forwarded Message
