MGM: don't do local redirect for shared filesystem if we are contacted via HTTP or from a FUSE client - fixes GITLAB #12

MGM: extend space-oriented policy configuration to OpenRead operation - this allows to define a policy conversion triggered by an Open for reading e.g. to push certain files from an erasure coded backend to an NVME pool if they are small

DOC: fix 'atime' configuration documentation - this is done only on space level, not on the subtree level

to avoid interference when we have several spaces balancing at the same time
which can lead to starvation of some spaces.

sure the newly built OFS library follows the XRootD conventions when it
comes to numbering otherwise the XrdSysPlugin will not be able to dlopen
and load the necessary symbols for it.

AUTH: Add the XrdSfsFileSystem API that is needed by other plugins to get a reference for the OFS object

was not yet computed so that we can make progress during repair.

is for a file systems that is not anymore in the list of attached stripes
for the given file and we already have the nominal number of stripes for
the concerned file.

We only checked the first element in the past leading to scheduler giving wrong
results in large EC placements. Fix this, also add tests to catch this

Fixes: EOS-6266
Signed-off-by: Abhishek Lekshmanan <abhishek.lekshmanan@cern.ch>

Fixes EOS-6132

the eosscitokens module.

The test.cmake script is meant to automate some of the standard
configure, build, test, install cycle during development, but also
for continuous integration. This script was originally started in
VecCore, then improved for XRootD, and now EOS. The script can be
generically called as

ctest -VV -S test.cmake

from the top directory of the repository. This will configure, build,
and try to run all tests with ctest. A build directory will be created
at the top level of the source directory automatically. The script has
several options to customize the build, the main ones are:

 -DCDASH=1            Enables submission to CDash dashboard
 -DCOVERAGE=1         Enables test coverage analysis with gcov
 -DMEMCHECK=1         Enables memory checking with valgrind
 -DSTATIC_ANALYSIS=1  Enables static analysis with clang-tidy
 -DINSTALL=1          Enables an extra step to call make install

When enabling coverage, a report is generated by default in the html/
directory inside the build directory. The results can be viewed by
opening the file html/coverage_details.html. This step can be disabled
by passing -DGCOVR=0 to ctest. It is recommended to use a debug build
to generate the coverage analysis.

The configuration can also be specified directly on the command line
via the -C option. For example, to run a coverage build in debug mode,
with less verbose output, and showing test output when a test failure
happens, one can run:

ctest -V --output-on-failure -C Debug -DCOVERAGE=1 -S test.cmake

Some environment variables can also influence the behavior of the
script, like CC, CXX, CMAKE_GENERATOR, CTEST_CONFIGURATION_TYPE,
CMAKE_BUILD_PARALLEL_LEVEL, CTEST_PARALLEL_LEVEL, and CMAKE_ARGS.
These are mostly self-explanatory and can be used to override the
provided defaults. For example, to build with the clang compiler
and use Ninja as CMake generator, one can run:

env CC=clang CXX=clang++ CMAKE_GENERATOR=Ninja ctest -V -S test.cmake

Finally, the script tries to load configuration files from the .ci
subdirectory in the source directory. The default configuration is
used if no specific configuration is found for the detected OS. For
example, on Ubuntu, a file named ubuntu.cmake will be used if present
instead of config.cmake. The script also tries to detect a version,
so, for example, on Alma, one could use almalinux8.cmake which would
have higher precedence than almalinux.cmake.