Repository navigation
fix(setup): don't fail when the run lock is owned by root - #2
Merged
Merged
Conversation
…block user runs A lock file left by a root run (e.g. first-boot unit) is 0644 root:root, so opening it for writing as the normal user failed with 'Permission denied'. flock works on a read-only fd; create the file only if it is missing. Claude-Session: https://claude.ai/code/session_01YMswzE32ygHazBu8EfzsdV
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.
A lock file left by a root run (e.g. the first-boot unit) is
0644 root:root, so a later run as the normal user failed with:The lock is now created only if missing and opened read-only (
flockworks on a read fd). This also avoidsfs.protected_regularrefusing root'sO_CREATon a user-owned lock in the sticky/run/lock.https://claude.ai/code/session_01YMswzE32ygHazBu8EfzsdV