Add logging to fairlock #693
Merged
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
Log to LOCAL2 at log level INFO when a lock is acquired and released, and when the client holding the lock sends anything through the socket (they can use this to identify themselves to the logging e.g. by sending "PID <PID>" Signed-off-by: Mark Syms <[email protected]>
KevinLCtx
approved these changes
Jun 21, 2024
rdn32
approved these changes
Jun 24, 2024
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.
Log to LOCAL2 at log level INFO when a lock is acquired and released, and when the client holding the lock sends anything through the socket (they can use this to identify themselves to the logging e.g. by sending "PID "
Extended from Tim's original change to actually pass PID and (monotonic) time from the client.