Cc pdlogs 61

Updated after review comments fro the ENT feature..  
Modified the messages to capitalize acronyms.  
Removed unnecessary whitespace.  
Added full stop to end of each part of the message.  
Actions are numbered if there is more than one action.  This separates the individual actions.
Separated the log definitions with a blank line to make them more readable.  
Ran astyle (according to the coding standards) against chronos_ent_definitions.h.
Fixed header file inconsistencies.
The review comment had: "A lot of the logs still say 'report issue to support' or something similar. This just isn't suitable for Project Clearwater."
The language was kept the same as this is what is done for the SNMP alarm definitions.  The associated documentation should identify the Metaswitch support team for ClearwaterCore and the Clearwater mailing list for Clearwater.
Removed signalnames.cpp.  The signal call name is now obtained from the strsignal call.
You are right.  That is what the developer log says.  Would you have a better explanation because I don’t know what the Reactor service is.

David

From: Eleanor Merry [mailto:notifications@github.com]
Sent: Wednesday, December 17, 2014 10:34 AM
To: Metaswitch/chronos
Cc: David Collins
Subject: Re: [chronos] Cc pdlogs 61 (#92)


In src/include/chronos_ent_definitions.h<https://github.com/Metaswitch/chronos/pull/92#discussion-diff-21984032>:

> +

> +static const PDLog CL_CHRONOS_STARTED

> +(

> +  PDLogBase::CL_CHRONOS_ID + 2,

> +  PDLOG_NOTICE,

> +  "Chronos started.",

> +  "The Chronos application has started.",

> +  "Normal.",

> +  "None."

> +);

> +

> +static const PDLog CL_CHRONOS_REACTOR_FAIL

> +(

> +  PDLogBase::CL_CHRONOS_ID + 3,

> +  PDLOG_ERR,

> +  "Fatal - Couldn't create the event reactor service.",

This doesn't feel like a user friendly log

—
Reply to this email directly or view it on GitHub<https://github.com/Metaswitch/chronos/pull/92/files#r21984032>.