Symbolic links to data not showing up in Hyrax 1.14.0 RPMs on CentOS 7
Description
Per Kent Yang <myang6@hdfgroup.org>, install of Hyrax 1.14.0 RPMs on CentOS 7 found that symbolic links don’t work, in spite of changing
BES.Catalog.catalog.FollowSymLinks=No
To
BES.Catalog.catalog.FollowSymLinks=Yes
And, from
BES.FollowSymLinks=No
To
BES.FollowSymLinks=Yes
Result: don’t see the symbolically linked served files.
However, if libdap and bes are built from from the source code can see the symbolically linked served files.
Per James, the problem is not the RPM packages per se, it is whether the BES is ‘configured’ using --enable-developer or not. If not, FollowSymLinks does not work. If ‘configure’ is run using --enable-developer, it will work.
Environment
Activity
So, there are two different behaviors, depending on where in the linked path the bes user is blocked from reading the linked directory. Suppose that the directory to be linked into the RootDirectory is /home/centos/hyrax/data and data's permissions are 700 (rwx, nothing, nothing), then the BES will show the link as a directory but will not permit the client to 'look in' that directory. If, OTOH, the data directory has perms 755 but the centos dir (or any dir above data) has permission 700, the link simply will not be shown, which is the same behavior as if the FollowSymLinks option was set to No.