Conflicts:
	upgrades/stager_2.1.14-13_to_2.1.14-14.sql

Fixed transfer.py, broken by a previous commit (reason not understood). This also fixes the d2d copies that were brokeb

Created custom exceptions for the scheduler component so that we avoid reusing standard ones when we should not

Fixed.

        - drop the 'persistancy on successful close' functionality as it is not used any long
        - connect to the diskmanager only when we have the necessary information, otherwise
        we are doing a d2d or an rtcpd transfer and we don't need to contact the diskmanager
        - remove unused include statements and fix formatting

        files to follow the naming convention used throughout the XRootD plugin

In a previous commit I removed the inheritance relationship between
ZmqSocket and ZmqSocketMT.  I used templated functions in order to
be able to handle instances of ZmqSocket and ZmqSocketMT with thei
same code.  I now believe that decision was wrong in the long run.
Future code maintainers will not know that a ZmqSocketMT object is
a type of ZmqSocket.  Eclipse and doxygen are very good at
providing class hierarchies.  One should benefit from this when one
can as it is a form of free documentation.

My previous commit not only removed inheritance, it also allowed
the multi-threaded version of ZMQSocket to contain the single
threaded version as opposed to inherit from it.  Using composition
over inheritance prevented future mistakes where somebody adds a
new thread-unsafe method to the super class and forgets or doesn’t
know that they should implement a thread-safe overriding version in
the sub-class.  This commit preserves composition over inheritance.

There are now three “ZmqSocket” classes: ZmqSocket, ZmqSocketST and
ZmqSocketMT.  ZmqSocket itself is now abstract and simply defines
the methods such a socket should implement.  ZmqSocketST is ai
concrete class for single-threaded use (hence ST) and
ZmqSocketMT is for multithreaded use (hence MT).

ZmqSocketST inherits from ZmqSocket and  ZmqSocketMT also inherits
from ZmqSocket.  ZmqSocketMT does not inherit from ZmqSocketST.
ZmqSocketMT contains an instance of ZmqSocketST therefore preserving
the composition over inheritance solution of the previous commit.

Conflicts:
	hsmtools/entersvcclass
	hsmtools/modifysvcclass

Fixed bug #104601: RFE : modify/enterSvcClass should check consistency of the GCPolicies when DiskPools are shared

Conflicts:
	hsmtools/entersvcclass
	hsmtools/modifysvcclass

Fixed bug #104601: RFE : modify/enterSvcClass should check consistency of the GCPolicies when DiskPools are shared

Fixed long options of listtranfers taking an argument. They were broken in their long version as getopt was not aware of the argument