jschoubben 8927d68900 Z4 zfs-manifest-bus: the events stream, states and ledger by template, the keeper as the module's one process bus account ...

The three root processes declare no bus and reach the keeper's socket; the module invokes the service manager's start. The judge refuses the keeper's bus emits and state until the validator accepts what the module asks for in requires (A-38).

Builds: design 42 zfs-owns-zfs §25, §26, §27, §28, A-6, A-19, A-36, A-37, A-38

2026-11-13 01:05:19 +01:00

..

testdata

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

applied_test.go

Z9 zfs-apply-run: the apply holds the lock, waits on a scrub or an unimported pool, and converges the node's id, ARC and pool

2026-11-13 00:34:58 +01:00

applied.go

Z9 zfs-apply-run: the apply holds the lock, waits on a scrub or an unimported pool, and converges the node's id, ARC and pool

2026-11-13 00:34:58 +01:00

apply_devices_test.go

Z8 zfs-apply-devices: cache and log devices converged by their stable names, after their checks

2026-11-13 00:32:06 +01:00

apply_devices.go

Z9 zfs-apply-run: the apply holds the lock, waits on a scrub or an unimported pool, and converges the node's id, ARC and pool

2026-11-13 00:34:58 +01:00

apply_properties_test.go

Z7 zfs-apply-properties: pool and dataset properties converged, read back and said

2026-11-13 00:27:31 +01:00

apply_properties.go

Z9 zfs-apply-run: the apply holds the lock, waits on a scrub or an unimported pool, and converges the node's id, ARC and pool

2026-11-13 00:34:58 +01:00

apply_test.go

Z9 zfs-apply-run: the apply holds the lock, waits on a scrub or an unimported pool, and converges the node's id, ARC and pool

2026-11-13 00:34:58 +01:00

apply.go

Z10 zfs-run: the scheduled run takes the lock, starts a due scrub and trim without waiting, and acts on hand acts

2026-11-13 00:38:17 +01:00

bus.go

A-37 the keeper: the module's one process bus account, a socket only root opens, and the root processes' bus through it

2026-11-13 01:04:41 +01:00

config_test.go

Z10 Z12 trim without day or time refused, keep count 0 removes nothing

2026-11-13 00:51:11 +01:00

config.go

Z10 Z12 trim without day or time refused, keep count 0 removes nothing

2026-11-13 00:51:11 +01:00

datasets.go

Add the zfs module, so the mesh can see the home server's pools and snapshot a dataset

2026-10-09 00:11:31 +02:00

events.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

follow_wake_test.go

Z14 zfs-follower: the follower starts the apply on the events that end a wait and keeps its findings in its own state

2026-11-13 00:49:01 +01:00

follow_wake.go

Z14 zfs-follower: the follower starts the apply on the events that end a wait and keeps its findings in its own state

2026-11-13 00:49:01 +01:00

follow.go

Z14 zfs-follower: the follower starts the apply on the events that end a wait and keeps its findings in its own state

2026-11-13 00:49:01 +01:00

hand_test.go

Z13 zfs-hand-acts: hand acts write their key and start the run; zfs_snapshot keeps a person's snapshots apart

2026-11-13 00:41:21 +01:00

hand.go

Z13 zfs-hand-acts: hand acts write their key and start the run; zfs_snapshot keeps a person's snapshots apart

2026-11-13 00:41:21 +01:00

health_module.go

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name

2026-11-13 01:03:17 +01:00

health_test.go

Z16 zfs-health: a refused or failed command in the applied state is unhealthy naming its key, and the module's own warnings

2026-11-13 00:55:17 +01:00

health.go

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name

2026-11-13 01:03:17 +01:00

helpers_test.go

Z9 zfs-apply-run: the apply holds the lock, waits on a scrub or an unimported pool, and converges the node's id, ARC and pool

2026-11-13 00:34:58 +01:00

io.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

keeper_test.go

A-37 the keeper: the module's one process bus account, a socket only root opens, and the root processes' bus through it

2026-11-13 01:04:41 +01:00

keeper.go

A-37 the keeper: the module's one process bus account, a socket only root opens, and the root processes' bus through it

2026-11-13 01:04:41 +01:00

machine.go

Z15 zfs-tools: zfs_config, zfs_snapshots_schedule, zfs_module_events, zfs_snapshots_check and zfs_findings read what the module owns, keeps and says

2026-11-13 00:54:06 +01:00

main.go

A-37 the keeper: the module's one process bus account, a socket only root opens, and the root processes' bus through it

2026-11-13 01:04:41 +01:00

manifest_test.go

Z4 zfs-manifest-bus: the events stream, states and ledger by template, the keeper as the module's one process bus account

2026-11-13 01:05:19 +01:00

parse_test.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

pools.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

properties.go

Add the zfs module, so the mesh can see the home server's pools and snapshot a dataset

2026-10-09 00:11:31 +02:00

review_test.go

Z13 zfs-hand-acts: hand acts write their key and start the run; zfs_snapshot keeps a person's snapshots apart

2026-11-13 00:41:21 +01:00

run_test.go

Z10 zfs-run: the scheduled run takes the lock, starts a due scrub and trim without waiting, and acts on hand acts

2026-11-13 00:38:17 +01:00

run.go

Z12 zfs-snapshots-remove: the run removes surplus scheduled ZFS snapshots only by their own record

2026-11-13 00:44:07 +01:00

schedule.go

Z10 zfs-run: the scheduled run takes the lock, starts a due scrub and trim without waiting, and acts on hand acts

2026-11-13 00:38:17 +01:00

scrub.go

Z10 zfs-run: the scheduled run takes the lock, starts a due scrub and trim without waiting, and acts on hand acts

2026-11-13 00:38:17 +01:00

snapshot_test.go

Z13 zfs-hand-acts: hand acts write their key and start the run; zfs_snapshot keeps a person's snapshots apart

2026-11-13 00:41:21 +01:00

snapshot.go

Z13 zfs-hand-acts: hand acts write their key and start the run; zfs_snapshot keeps a person's snapshots apart

2026-11-13 00:41:21 +01:00

snapshots_prune_test.go

Z10 Z12 trim without day or time refused, keep count 0 removes nothing

2026-11-13 00:51:11 +01:00

snapshots_prune.go

Z10 Z12 trim without day or time refused, keep count 0 removes nothing

2026-11-13 00:51:11 +01:00

snapshots_take.go

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name

2026-11-13 01:03:17 +01:00

snapshots_test.go

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name

2026-11-13 01:03:17 +01:00

templates_test.go

Z1 Z2 Z3 zfs-manifest: packages and values, files and units, the apply and the run in the declared order

2026-11-13 01:00:42 +01:00

tools_config_test.go

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name

2026-11-13 01:03:17 +01:00

tools_config.go

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name

2026-11-13 01:03:17 +01:00

tools.go

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name

2026-11-13 01:03:17 +01:00

watch.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00