Usage differences for the "symlink" action
The "symlink" action has usage differences between FileStore (NS3) and ObjectStore (NS4).
Symlinks and directories with the same name
- FileStore: Not Supported — A symbolic link and a directory that exist within the same parent can not have the same name.
- ObjectStore: All path names are treated independently of all other path names. Therefore, symbolic links and directories within the same parent can use the same name.
Trailing slashes (“/”) in symlink names
- FileStore: Not Supported. — “/” can only exist as path separators.
- ObjectStore: Since a traditional file system is not in place, any number of trailing slashes can be included at the end of a symbolic link name.
Non-existent directories in a specified path
- FileStore: When a path is specified, if any sub-directory along that path does not currently exist, FileStore will create it as a physical directory, and house the symbolic link in the last directory named in the path.
- ObjectStore: The final value noted in the path will be used as the name for the symbolic link. Any non-existent directory within that path will be set up as Implicit, and will be associated as such with the newly created symbolic link.
Note: The same rules that apply to the mkdir action for ObjectStore, in regards to trailing slashes (“/”), and periods (“.”) in a directory name also apply to any directories established in a path for the symlink action.