[CBR-345] Create symbolic link for log files.

[365andreas]

Description

Create a symbolic link for every log file created for UNIX-like systems. Symbolic link will follow the latest active log file.

For example:

• logs/node -> node-20180919092116
• logs/node-20180919091013
• logs/node-20180919091536
• logs/node-20180919092116

This allows a tail -F to follow the log files even when they are recreated under log rotation.

Also, create the log prefix directory on startup if it does not exist.

Linked issue

CBR-345

Type of change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• 🛠 New feature (non-breaking change which adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
• 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
• 🔨 New or improved tests for existing code
• ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

• I have read the style guide document, and my code follows the code style of this project.
• If my code deals with exceptions, it follows the guidelines.
• I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
• CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

• I have added tests to cover my changes.
• All new and existing tests passed.

QA Steps

Screenshots (if available)

[CodiePP]

rebased on develop