I can't seem to find too much information on whether this is feasible or not.  I did come across an old thread, http://lime-technology.com/forum/index.php?topic=3243.msg27494#msg27494, mentions creating symbolic links on disk shares that can then be accessible via user shares, but it didn't really address my question.

 

Will those symlinks be completely "accessible" (i.e. access the real "target" and not treat the symlink as a file itself) by network clients access unRAID via SMB and/or NFS?

I can't seem to find too much information on whether this is feasible or not.  I did come across an old thread, http://lime-technology.com/forum/index.php?topic=3243.msg27494#msg27494, mentions creating symbolic links on disk shares that can then be accessible via user shares, but it didn't really address my question.

 

Will those symlinks be completely "accessible" (i.e. access the real "target" and not treat the symlink as a file itself) by network clients access unRAID via SMB and/or NFS?

I do this for files I am accessing via SMB for playing via my ATV2+ATV Flash Media Player.  This works fine.  I do it so I can have media (in particular movies) accessed via more than one path without duplicating the files.

 

I am not sure if it works for all clients.  I am also not sure what happens if you delete the underlying file or the symlink version.

What about a symlink to a directory?

What about a symlink to a directory?

It's working for me.

I'm not the brightest *nix bulb in the tool chest, hence my questions.  And when I attempted to perform "ln -L" unRAID shot back with "hard link not allowed for directory" so I'm assuming that the symlink will not be automatically updated whenever the source is moved or removed.

 

So far I am able to access the symlink to the directory from a SMB client as if it where it's own "entity," which is my goal.

I'm not the brightest *nix bulb in the tool chest, hence my questions.  And when I attempted to perform "ln -L" unRAID shot back with "hard link not allowed for directory" so I'm assuming that the symlink will not be automatically updated whenever the source is moved or removed.

 

So far I am able to access the symlink to the directory from a SMB client as if it where it's own "entity," which is my goal.

I have been using soft links rather than hard links.

A follow up...

 

I tried creating a symlink but the problem is the symlink is not "visible" from a client if the symlink is not residing in the same directory of the source file.  UnRAID can see it just fine via the "ls" command; the switch "-l" shows the link to the source file.

 

Whether I create the link into another directory, or move it to another directory, it doesn't matter: if it's not located in the same directory it's not "accessible" by a client machine via SMB (I haven't tried via AFS nor NFS).  I was quite positive I was able to do this before (I don't resort to links that often), but this is baffling to me.

 

I ran the New Permissions util but that didn't resolve it.  I logged in as root (the same account that I used to create the link via telnet) and other users and neither did that help.

 

Can anyone shed light on what I'm doing wrong or what could be causing this?

And could this be an issue with rc16?

 

Or is this perhaps an issue between creating links of an actual file (an ISO) versus creating links of a directory?

 

I've successfully created symlinks in other directories under previous rc versions, but they were all of directories.