Dear Stephen, thanks for reaching out and your report.
Please be aware that the current maintenance team is the 3rd generation. We are not the founders of Back In Time (BIT) and still do investigate the behavior of BIT. But we are on track! ;) On 2024-02-26 02:43 sgc...@gmail.com wrote: > On 25 February I noticed that backintime (root) had not done any > backups since 18 February I am sorry to hear that. It sounds familiar to some of our known bugs. My team mates are deeper in that area and will point you to it. Being silent for 7 days not doing any backups is another topic we do have on our list. We think about how we can make BIT more verbose in that situation. See: - <https://github.com/bit-team/backintime/issues/450> - <https://github.com/bit-team/backintime/issues/1018> > Is backintime (root) capable of handling interruptions caused by a > reboot? It should, yes. It can resume backups. > Is there a lock file that is only cleared after a reboot or > completion of a backup? There are several lock files. This is one topic we do investigate. Our current results about that research are summarized in this developers documentation. <https://github.com/bit-team/backintime/blob/dev/common/doc-dev/4_Control_files_usage_(locks_flocks_logs_and_others).md> Thanks in advance Christian Buhtz _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-le...@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: arch...@mail-archive.com
