Comment # 3 on bug 972984 from Kristyna Streitova

This is the same issue as bug 980873 that we've just closed as invalid. Using
zero-length lock files is common Unix practice and we believe that this is the
problem with third-party software that shouldn't alter the ctime timestamp.

I'm sorry, but I'm closing this issue as invalid.


(In reply to Ulrich Windl from comment #0)
> Another note: This may be a duplicate of Bug 960716, but the former had been
> closed as being invalid while it seems to address the same issue.

Btw. That was a little bit different issue about an inability to set the custom
times for hourly, daily, weekly and monthly scripts with the current version of
the run-crons script. However, we figured out that this is possible and the
SLE12 manual provides a solution (see comment 2). So no changes in the
run-crons script were needed.