We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Werk #10690: mk_logwatch supports single backslash in Windows paths

ComponentChecks & Agents
Titlemk_logwatch supports single backslash in Windows paths
Date2020-03-23 10:18:24
Checkmk EditionCheckmk Raw Edition (CRE)
Checkmk Version1.7.0i1
LevelTrivial Change
ClassNew Feature
CompatibilityCompatible - no manual interaction needed

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.