Open anonymous352 opened 6 years ago
Any idea if this is a bug or intended behaviour ?
I submit this is in fact a bug, although it may have been the original intended behavior. Design bugs happen, just as code bugs do.
The problem is actually worse than what you describe. Even if /etc/cron.d/timeshift-hourly exists, if it has been modified, it gets overwritten with what the original looked like. This behavior is inconsistent with application norms for the design of how applications use configuration files. By overwriting the configuration file, the behavior is not really configuarable, it is essentially hard-coded.
Another comment on this is that if you try to configure alerts with something like halthchecks.io, the cron file gets overwritten after the first run.
I've noticed that Timeshift adds a crontab file in /etc/cron.d named timeshift-hourly if one does not exist, even if Timeshift runs with or without error. I have only configured Timeshift for running at '@reboot' time and no other times. As a result I have to keep removing this unwanted timeshift-hourly file as I do not want it to run hourly at all. Any idea if this is a bug or intended behaviour ?