First one was a block not being pushed whe the end of file was reached, the other one was the use a NULL pointer if we fail to position the tape

Which was not making any sense

Now the all are into AutoReleaseBlock.hpp and the class has been templated to take into account the 2 types of MemoryManager

Excute is now simpler, some dead code has been removed, so does Payload::EndOfFile, which is now castor::tape::exceptions::EndOfFile

initialized some mebers that were not and a some log in case of error while opening the session

and DiskReadThreadPool

Conflicts:
	castor/tape/tapeserver/daemon/DiskWriteThreadPool.hpp

Compute it on DiskWriteTask and report it to the Client. Tests and interfaces have changed consequently

Renamed member variables to canonycal m_
Renamed TaskInjector->end to TaskInjector->finish() to match other threads conventions.
Fixed missing finish() in RecallTaskInjectorTest
Added missing finish() call in TapeReadTSingleThread.

Fixed missing member initialization
Fixed missing last call flag
Adpated to the injection of the NULL pointer as the end of session indicator.
Fixed missing path indication in the recall description.

added a thread logging parameter, indicating the thread involved
added startup and finish log messages for threads.

The old rmd daemon is now used to mount and unmount tapes in SCSI
libraries.