Provide clear meaning to the log levels

[lpetre-ulb]

Brief summary of issue

Development and debugging are sometimes slowed by the lack of complete debugging information. On the other hand, the log is filled with nearly useless messages in which the relevant information is lost for some routines.

Types of issue

• Bug report (report an issue with the code)
• Feature request (request for change which adds functionality)

Expected Behavior

1. Developers (and even user) should be able to choose the log level. It could be done at compile time for the RPC modules, at load time in rpcsvc or at runtime with a new function. The last option is the most versatile, but would require either to patch rpcsvc or to use another logging system.

2. A clear meaning should be given to the 7 (!) log levels. Some of them could be unused, or rarely used.

Current Behavior

1. The log level is set at compile time in rpcsvc. When the log level given to log_message is below that value (currently INFO) the message is not forwarded to the syslog daemon. The only solution is

2. Some messages have a too high log level and then "pollute" the logs.

Context (for feature requests)

It happened to degrades the debugging experience.

Your Environment

• Version used: ab4ddd0