mesh-host

Files

T

jschoubben 46c16e18fe Name a filesystem by its UUID, its kernel id or its source, and keep nothing that has no name (hq ADR 0325 fifth review)

NFS and FUSE report a zero f_fsid, so another export or another FUSE mount at the
same point was named alike and kept without a warrant; xfs's f_fsid follows the
device number. A filesystem is now named by its UUID (its device matched in
/dev/disk/by-uuid), else a nonzero f_fsid, else mountinfo's source; one that cannot
be named is never kept or taken. Entries left on a filesystem not back within 30 days
are forgotten, said once, and the naming read is shared per mount.

2026-10-12 19:14:42 +02:00

declared_keys_test.go

Give a service's held state its own field and key, so main compiles again

2026-10-09 03:03:58 +02:00

declared_test.go

A node that loses its mesh comes back on its own

2026-08-29 20:17:49 +02:00

declared.go

Refuse a declaration for the other mode, or older than the mesh's last, and say what an apply would change first

2026-09-23 23:15:28 +02:00

former_test.go

A take is a comparison: the host's facts, former targets, and strays (hq ADR 0163)