A benign exception failed to be caught and led to unnecessary errors.

The locking of the scheduler global lock is retained so only on drive can create a mount at any point in time.

Copying SSS of taped to the official location (temporary fix, should be created here on the flyx by default)

Compile switches now applied to each target separately, cta_admin has
instrumentation switched off.

Rao branch

See merge request !4

If the whole contents of the ARCHIVE_FILE and TAPE_FILE tables are
listed without a search criteria and with an ORDER BY clause then the
first row back from the database will take a relatively long period of
time to be returned.  This is because the database will have to sort
every row before returning the first.  This long period of time will
cause the current (non SSI) cta command-line tool to time out.

The installation in the buildtree environment is not useful as all is pre-installed in the image.

Changed default location of cta-taped config file within the cta-taped command-line arguments to /etc/cta/cta-taped.conf

View the binary contents of the Protobuf received on the client side to
debug ParseFromArray() error

Also outputs stderr on success as well as failure

Command will remove drive or drives by regex from the drive register.
The drives must be in state Down unless --force option is set.
Usage: rm <drive_name> [--force/-f]

If there is any active tapeserver with this drive it will create the
entry in the drive register again with Down status.

Example of the usage:
  cta drive rm ^VDSTK
  Drive VDSTK41 in state Free and force is not set (skipped).
  Drive VDSTK42 removed.

This would detect instances where rados reports an object deletion before is actually happens.