Connection: add USERDEBUGDIR environment variable #24
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
|
I think without documentation nobody will ever know how to use it. Can you add some docs? Not sure if it's practical to add tests, too. |
|
+1 for the PR |
|
Oh wow here's a blast from the past! I haven't been running DJabberd for years. Nice to see someone is still maintaining it. |
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.
We use a similar pattern with our other production services. Configure a directory in which per-user subdirectories can be created, and then if that directory exists, create one file per connection with copious debug data.
This is very useful for single-user debugging by support, they just do a 'mkdir' and then pass the ticket on to third line (me!), who already have a protocol dump by the time they need to start debugging.