Moved safety period of synchronization to 10mn after the file closing rather than one (can be short in case of extreme load)

constraint is too visible in the DB, so it is postponed to the next
major version and it will require a non transparent upgrade.
Also prepared skeleton script for 2.1.15 including that step.

Avoid to loop on DBMS_ALERT.SIGNAL on bulk operations. This involves
both the request handler on bulk PrepareToGet requests and the
Disk2diskCopyJob bulk handling.

thread-safe

Further fixes on top of previous commit, still related to SR #140319.
We can't ensure no one creates entities connected to a CastorFile as
in particular draining and rebalancing activities may create many
Disk2DiskCopyJob entries in bulk without taking locks on the
corresponding files. Thus we have to compensate to constraint violation
errors.

and used by RAL...

Fixed bug #103175: Concurrent recalls that fail concurrently may create a deadlock if they share files

Corrected the C comment explaining the modification made by this RFE.

bug #103138: RFE: rtcpd should not space the tape backwards and forwards when recalling

Fixed in the master branch.

Changed the maximum numbers of jobs failed in one go by the synchronization from 10K to 1K in order to not overheat the DB

Moved the remaining configuration files from CASTOR/debian to the directories where their respective Imakefile files are located

Fixed in the master branch.

configuration scripts