1. 18 Mar, 2015 1 commit
  2. 04 Dec, 2014 1 commit
  3. 03 Jul, 2014 2 commits
  4. 15 May, 2014 1 commit
  5. 14 May, 2014 1 commit
  6. 16 Jan, 2014 1 commit
  7. 15 Jan, 2014 1 commit
  8. 24 May, 2012 1 commit
  9. 16 May, 2012 2 commits
  10. 09 Nov, 2009 1 commit
  11. 18 Aug, 2009 1 commit
  12. 04 Feb, 2009 1 commit
    • Steven Murray's avatar
      Added the CASTOR_DLF_WRITEPC macro. · b63bb04d
      Steven Murray authored
      This macro should be used when it is desirable to include the file, line and
      function context information in a log.  It is advised to include such
      information when logging an error for the developers, but not to use it for
      monitoring logs where operators are informed of what is happening and they do
      not need or want to know the details of the source code.
      
      The CASTOR_DLF_WRITEPC macro macro generates the file, line and function
      context information automatically and passes it on down the DLF logging chain.
      This means developers do not need to use the __FILE__, __LINE__,
      __PRETTY_FUNCTION__ macros in their application code when logging.  Here is an
      example of using this macro:
      
        try {
          ...
        } catch(castor::exception::Exception &ex) {
          castor::dlf::Param params[] = {
            castor::dlf::Param("volReqId", vdqmJobRequest.tapeRequestId),
            castor::dlf::Param("Message" , ex.getMessage().str()       ),
            castor::dlf::Param("Code"    , ex.code()                   )};
          CASTOR_DLF_WRITEPC(cuuid, DLF_LVL_ERROR, AGGREGATOR_MAIN_SELECT_FAILED,
            params);
        }
      b63bb04d
  13. 22 Aug, 2008 1 commit
    • Steven Murray's avatar
      Added nice error message already created but ignored from a failed invocation · 8336286a
      Steven Murray authored
      of ::dlf_init() to the exception thrown by:
      
      castor::dlf::dlf_init(const char* facilityName, castor::dlf::Message messages[])
      
      A nice explanatory message was being consructed when the facility name exceeded
      21 characters in length, but the message was not added to the exception, so I
      only got a "Unable to initialize DLF" with no further explanation when I tried
      to initialise DLF with a crazy long name.
      8336286a
  14. 20 May, 2008 1 commit
  15. 14 Mar, 2008 1 commit
  16. 10 Mar, 2008 1 commit
  17. 05 Mar, 2008 3 commits
  18. 17 Aug, 2007 1 commit
  19. 16 Aug, 2007 1 commit
  20. 18 Jul, 2007 1 commit
  21. 25 Sep, 2006 1 commit
  22. 13 Jun, 2006 1 commit
  23. 11 Apr, 2006 1 commit
  24. 05 Apr, 2005 1 commit