Opened 5 years ago

Last modified 2 years ago

#11542 assigned defect

Add a new logging domain for transport proxies

Reported by: wfn Owned by: yawning
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-pt intro logging
Cc: asn, yawning Actual Points:
Parent ID: Points: small
Reviewer: Sponsor: SponsorT

Description

velope suggested (and nickm is not against the idea of) adding a new logging domain for all the stuff to do with transport proxies / PTs. It would sure be nice to have transport proxy output like #9957 go to that specific domain; it would make debugging PT things easier, I think.

Does this make sense, or is there simply no need for it, really?

Child Tickets

Change History (12)

comment:1 Changed 5 years ago by asn

I think it makes sense, and I could imagine it being useful.

For example, if people trying to debug obfsproxy with #9957 get lost in the info-level logs of Tor, we could ask them to only look at LD_PT log messages.

We are currently using a mixture of LD_GENERAL and LD_CONFIG for PT-related messages.
I'm mainly using LD_CONFIG for log messages related to the PT configuration protocol, but I think even those can be switched to use LD_PT.

More opinions are welcome.

comment:2 Changed 5 years ago by nickm

I have no objection. When writing a branch for this, if there are going to be a bunch of log messages that change their domains, please have one of the commits do nothing besides change domains. That will make it easier to review the other stuff.

comment:3 Changed 4 years ago by yawning

Keywords: TorCoreTeam201508 added

comment:4 Changed 4 years ago by yawning

Owner: set to yawning
Status: newassigned

comment:5 Changed 4 years ago by nickm

Keywords: TorCoreTeam201509 added; TorCoreTeam201508 removed

comment:6 Changed 4 years ago by yawning

Keywords: 028-triaged added; TorCoreTeam201509 removed
Milestone: Tor: 0.2.???Tor: 0.2.8.x-final
Points: small
Sponsor: SponsorT

comment:7 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

Move a bunch of (but not all) low-priority items to 0.2.???. If you write a patch, it can still get into 0.2.8

comment:8 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:9 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:10 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:11 Changed 2 years ago by nickm

Keywords: 028-triaged removed

comment:12 Changed 2 years ago by nickm

Keywords: intro logging added
Severity: Normal
Note: See TracTickets for help on using tickets.