1 Title: Fixed DST shift correction for downtimes, causing CMC to use 100% CPU
10 When a downtime was configured to recur every hour and a 1h DST shift
11 happened, the CMC would go into an infinite loop with 100% CPU load and no
12 monitoring at all. If the downtime in question was set in an ad hoc fashion
13 via the GUI (not via rules), the only way to work around this issue was to
14 remove the state file, losing all downtimes, acknowledgements and comments.