Moved the building of the unit tests out of the client only compilation as it requires server libraries for linking.

Bumped up the time waited before cheking that the killed child process is gone from 10ms to 100ms as 10ms was too small in some cases (helgrind + slow virtual machine).

user errors.  This commit adds the following macro that helps enforce
that convention and document it in the code.
  "#define LOG_USERERR LOG_NOTICE"

that exceeds the permitted maximum of syslog from the
LoggerImplementation::logMsg() method to the
LoggerImplementation::reducedSyslog() method.  I have done this because the
reducedSyslog() method is the one that does the actual work of sending the log
message syslog via a send() over a local UNIX socket.

not on my development box:

castor/log/LoggerImplementation.cpp: In member function 'size_t castor::log::LoggerImplementation::determineMaxMsgLen() const':
castor/log/LoggerImplementation.cpp:62: error: 'atoi' was not declared in this scope
castor/log/LoggerImplementation.cpp:80: error: 'atol' was not declared in this scope
castor/log/LoggerImplementation.cpp: In member function 'std::string castor::log::LoggerImplementation::cleanString(const std::string&, bool)':
castor/log/LoggerImplementation.cpp:372: error: 'free' was not declared in this scope

Dennis used within ithe LoggerImplementation class with C++ std::ostringstream
code.

The castor::log::Param class simply contains an std::string name and an
std::string value.  The new templated constructor of the Param class uses
std::ostringstream to convert a non-string value to a string one.

identified ares of the new logging code that should be removed.  I will
remove them in a future commit so that we can come back to this one if we
decide the removals were too much.

CASTOR framework via the class castor::server:BaseServer.

Constructive feedback, and better still modifications, are warmly welcomed.

LoggerImplementation.  This then allowed me to rename the writeMsg()
suit of functions to logMsg() which is much more clear.

as a parameter.  The functions that create the CASTOR daemon objects all
create a castor::log::LogImplementation object and pass it to the constructor
of their corresponding CASTOR daemon object.  When unit testting, one now has
the posibility to develop a dummy Log object that implements the interface
with dummy or mock routines so that the unit tests can run without having to
write to syslog or rsyslog which is a bit heavy for unit tests.  The
castor::log::LogImplementation basically contains the logging code centered
around syslog that was developed by Sebastien and Dennis.

Please note that I now have to add one or more log functions to the base
class of the CASTOR daemon objects, namely castor::server::BaseServer.

the following MACRO magic in h/log.h:

  #ifdef log
  #undef log
  #endif
  #define log (*logfunc)          /* logging function name                */

With this commit I remove the above MARCHO magic and simply replace "log" with
its expanded form of (*logfunc).

later on.

options to DiskManager/*PendingTimeout to improve usability.

affecting draining operations.

Completed the fix to take into account disk-to-disk copies failed
at the start.
To have a full tracking, a src diskcopy ID field has been added
to Disk2DiskCopyJob, and populated at start time when available.

Fixed tight loop on errors when filesystems of the gcd are badly configured. This could go up to 10KHz !

idea being you might simply want to log a message with no parameters.

  /**
   * Writes a message into the CASTOR logging system. Note that no exception
   * will ever be thrown in case of failure. Failures will actually be
   * silently ignored in order to not impact the processing.
   *
   * Note that this version of writeMsg() implicitly uses the current time as
   * the time stamp of the message.
   *
   * @param priority the priority of the message as defined by the syslog API.
   * @param msg the message.
   */
  virtual void writeMsg(
    const int priority,
    const std::string &msg) throw() = 0;

However, this is to be evolved to a more robust schema, where
DISABLED hardware for too long is deemed not to have any transfer any
longer and won't stop the synchronization from being executed on the
rest of the cluster.

affecting draining operations.

Fixed all items mentioned in the ticket, plus added a timestamp column
on DrainingErrors that is shown by draindiskserver -q -f.
Furthermore, as DrainingErrors now contains a reference to DiskCopy,
draindiskserver -q -f prints the full path of the failed draining DC.

- to missing req or subreq UUIDs
- to exceptions (e.g. from cx_Oracle) that would throw AttributeErrors

Moved multi process tests into a new binary, as memcheck fails them (a lot of test framework related structures are still allocated at exit time).

Fixed wrong reading of /sys files.
Added unit tests.