General User Release Notes
3.4 Symbolic Links Implementation Changes
For example,
$ CREATE /SYMLINK="/SYS$HELP/CC_RELEASE_NOTES.PS" RELNOTES.PS
$ DIR /SIZE /NOSYMLINK RELNOTES.PS
Directory SYS$SYSROOT:[SYSMGR]
RELNOTES.PS;1 209
Total of 1 file, 209 blocks.
3.4.2 Audit Alarms Fixed
V8.4
With the previous implementation of symlinks, when commands such as $DIR
attempted to list a directory, it resulted in audit alarms if the user did not have
permissions on the target of a given file. DIRECTORY command must read the
file header (that is, perform a file access operation) in order to determine if the
file was a symlink. This access will trigger the audit alarm if the user issuing
DIRECTORY command does not have read permissions on the target file. This
problem has been corrected with the new symlink design on OpenVMS Version
8.4, where a directory entry indicating a symlink is flagged as such, with DIR$V_
SPECIAL set to 1 (overlaid with DIR$V_NEXTREC).
Note
• Compatibility with symbolic links created by OpenVMS Version 8.3
Symlinks created by OpenVMS Version 8.4 will work on OpenVMS
Version 8.3. However, symlinks created by OpenVMS Version 8.3 will
not work on OpenVMS Version 8.4.
To convert symlinks created by OpenVMS Version 8.3 to the
format required on OpenVMS Version 8.4, you must run the
ANALYZE/DISK_STRUCTURE (VERIFY) utility with the /REPAIR
qualifier.
3.5 SHOW SYSTEM/STATE=MUTEX Does not Display the
Processes
V8.4
$ SHOW SYSTEM/STATE=MUTEX
command does not display the processes in MUTEX
state.
However, you can display the processes in MUTEX state by entering the following
command:
$ SHOW SYSTEM
3–2 General User Release Notes
