Fix wireguard to detect launchd on Monterey #7
Conversation
This file contains 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
palmerc
force-pushed
the
monterey-launchd-fix
branch
from
0f519a9 to
de363a2
Compare
palmerc
force-pushed
the
monterey-launchd-fix
branch
from
de363a2 to
c9adc69
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have noticed that wireguard no longer starts on Monterey as a launchd service. Investigation suggests that the check for 'domain' in the output of
launchctl procinfo $$no longer works. I have switched the logic to check for the '(pid XX is not managed by launchd)' message instead which works on Big Sur and Monterey in my testing.