ncm-cdispd code cleanup

Work in progress related to #8...

Discussion on cleanup goals is better placed in #8.
I suppose that I have no other choice if I want to see this PR merged... I'm hesitating to go further in this discussion even though I don't understand your arguments. This is not because an improvement is not perfect that it should not be made if it is a step in the right direction. Switch to log4perl is probably something to consider but this is much more work and certainly not something we'll do in the short term, I'm afraid.

As for changing the rsyslogd configuration, IMO, this is exactly the wrong way to do it. The limit is not the problem: it is here to protect against potential denial of service. This is why I consider that being a good citizen means coping with this limit and not impose to increase it at the risk of allowing others to do a real DoS. I think that my approach (may be not my implementation!) is the right one. And if not perfect, it offers a rather clean solution to a very limited problem: this particular case is probably one of the only place where we may want to send 500 to 1000 lines in one go to syslog. `ncm-cdispd` needs to do it the right way to be a good citizen. And a user, if asking for this information, probably wants to see it untruncated.

Remember that in the last version of the implementation (that I forgot to push) there is no more penalty if you don't run `ncm-cdispd` with --debug, something done only by developers in rare circumstances (but in these circumstances they probably want syslog to be readable by a human rather than a program!).

I realized that I didn't resist to argue once more!