Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 6fd8b87670587e0e7ed315958f98bf92334e9280 https://github.com/tribe29/checkmk/commit/6fd8b87670587e0e7ed315958f98bf923… Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com> Date: 2020-03-24 (Tue, 24 Mar 2020) Changed paths: A .werks/10690 Log Message: ----------- 10690 mk_logwatch supports single backslash in Windows paths In previous versions it was needed to escape backslashes with another backslash. This has been cleaned up now. You could leave your configuration untouched and it still works as before. In a rare case, if your configuration contains double escaped backslashes, i.e "\\\\" or even "\\\\\\", this change will result in one old service being removed and one new services being discovered. For example, the service "LOG C:\\\\Back\\test.log" previously discovered as "LOG C:\\Back\test.log" will be discovered now as "LOG C:\Back\test.log". In this case you will have to rediscover the related Log services on your hosts. We recommend finding and replacing the escaped backslashes (if any) with plain backslash "\" for better usability. You do not need to rediscover services again. In case you have configured "Logwatch to Event Console forwarding", you may have to update your forwarding and Event Console rules to match the new log path. Change-Id: I2d1bd6e071d6a6984a9aa6c6541033246060a6eb Commit: 6f5920d7260aa7b39f338b469ec0089e7c13fd6a https://github.com/tribe29/checkmk/commit/6f5920d7260aa7b39f338b469ec0089e7… Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com> Date: 2020-03-24 (Tue, 24 Mar 2020) Changed paths: A .werks/10691 Log Message: ----------- 10691 mk_logwatch supports UTF-16 LE BOM encoded files Since this release mk_logwatch is able to process files encoded with UTF-16LE. Those files must have correct byte order mark(BOM). This type of encoding is used usually by Windows software. Change-Id: I251b8b7f762d03849c9127a33be0134cdad9cb79 Compare: https://github.com/tribe29/checkmk/compare/27de005dab1f...6f5920d7260a