teardown strands the boot daemon when config no longer has dedicated addresses #2
Labels
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
carvers/silta#2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
apply_teardown(src/setup.rs:389) returns early when the current config has no dedicated addresses, skippingremove_boot_daemonand the /etc/hosts block removal. An installed boot daemon then survives the teardown the README says always removes it.Failure scenario: user does
sudo silta setup --persistent, later rewrites the config to plain 127.0.0.1 forwards (dropping bind_address), then runssudo silta teardownto clean up.plan()is empty, teardown prints "nothing to remove" and exits without touching the LaunchDaemon plist, the feth99 interface, or the /etc/hosts block. The root boot daemon keeps running setup with the new config at every boot, and there is no silta command left that will remove it.Fix direction: teardown should remove the daemon and any existing hosts block by interface name regardless of whether the current config declares dedicated addresses.
Source: high-effort code review, CONFIRMED. Area: setup.