Repository navigation
fix(worker): leave a systemd-managed infernet daemon alone; v0.2.30 - #46
Merged
Merged
Conversation
dev2 runs infernet under its own infernet.service AND the worker started a second daemon on the same config dir. They fought over the socket, port and pidfile: infernet.service restarted 347 times, and the v0.2.29 reaper killed the systemd daemon once because it was not the pid in daemon.pid at that moment. - infernet_systemd_managed(): when infernet.service is active the worker does not start a daemon and does not run `infernet update` (the daemon auto-updates itself every 5 min). - reaper: only daemons in the worker's own cgroup are candidates. - Bump to 0.2.30, including the release feed's FALLBACK_VERSION. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan8 finding(s) MEDIUM: 8
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #43 after rolling v0.2.29 out on dev2.
dev2 also runs infernet under
infernet.service. The worker started a second daemon on the same config dir, so they fought over socket/port/pidfile (infernet.serviceNRestarts=347), and the v0.2.29 reaper killed the systemd daemon once because it wasn't the pid in daemon.pid at that instant.infernet.serviceis active, the worker neither starts a daemon nor runsinfernet update(the daemon auto-updates itself).cargo test -p c0mpute-cli: 13 passed.🤖 Generated with Claude Code