5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	7f05fad58a	restic: judge no night overdue where nothing is declared, and a count's age by the time the machine was awake ... A machine that backs up nothing read as missing its night after 26 hours up, and a laptop's count, last written before it slept, read as stale on waking until the next look (novox/hq issue 489).	2026-10-11 21:10:11 +02:00
jschoubben	7211227c76	restic: let a restore point taken by hand go only after a night recorded good, say a missing hand= as a file to push, and say what a failed thinning already let go (novox/hq issue 453)	2026-10-11 17:57:43 +02:00
jschoubben	879bc4bca2	restic: keep a backup taken by hand past the next thinning, until a later night and keep-hand-taken-days, so the restore point taken against a risky change is still there when it is needed (novox/hq issue 453)	2026-10-11 12:28:17 +02:00
jschoubben	cbe9fa7a2c	restic: raise a night that never happens, and have the mesh write the retention readable (novox/hq issue 454) ... A hung night, a lock held for hours or a lock that cannot be taken left no failed night behind, so it stayed healthy. The night's process now counts how long the machine was up since its newest good night, by the monotonic clock so a sleeping laptop is not blamed, and past 26 hours it is raised. The retention file is written 0644 and root's instead of read through sudo: the account reads it and still cannot change it. An unreadable file names its cause, and the healthy answer says only what was seen.	2026-10-11 12:14:54 +02:00
jschoubben	d649309895	restic: raise a failed backup, a failed thinning and a refused retention as the module's health (novox/hq issue 454) ... A failed night was a journal line only, so a typo in a retention setting let the repository grow until a disk filled. The night and the measuring now run as processes the node-engine judges: the night by backup_health, which is unhealthy for a module not backed up, a night that did not run, a failed thinning or a missing retention file, and waits naming the setting when one is refused; the measuring by its unit. A file lock keeps a night and the tool runtime's now and restore apart. The retention file is root's alone, so the account reads it through sudo: until now every night would have refused it as unreadable. Every machine has the file, so a missing one is refused instead of thinned by 14/8/6. backed-up says the retention in force and the last thinning per module.	2026-10-11 11:56:23 +02:00