nfs-server: check every share against where the backup seat keeps its data, on every pass (review follow-up of #136)

+968 -20

4 Commits

Author	SHA1	Message	Date
jochen	26f9c6e10d	nfs-server: one test per guard (each stray guard, the failed-reload retry, the empty data list, the walk's stop, a stopping pass); say that a start drops hand-made exports and that unknown backup paths are a deliberate warning (review of #142 ) mesh/merge-gate pass: builds nfs-server, sent nowhere; no bus step; 1 wait(s) for a person; every machine composes with the change as it did without (4 of … Details mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) Details mesh/delivery superseded: a newer delivery to the same trunk took over its walk Details	2026-10-09 14:45:03 +02:00
jochen	7320d99a11	Make nfs-server reconcile the kernel's exports with its file, so a failed reload or a withdrawn grant is not left exported while the module says it is healthy; warn on a stale or unknown backup list	2026-10-09 14:43:32 +02:00
jochen	72a6d062dc	Let SIGTERM cancel a running pass and bound nfs-server's clean-up at 10 s, so a hanging command cannot keep the export file past the stop timeout	2026-10-09 14:43:32 +02:00
jochen	87d6a5549c	Check every share against where the backup seat keeps its data on every pass, so the hour a clean look is believed cannot hide a new repository	2026-10-09 14:43:32 +02:00

nfs-server: check every share against where the backup seat keeps its data, on every pass (review follow-up of #136) #142