Opened 7 years ago
Last modified 2 weeks ago
#5148 new task
SIGHUP managed proxies when logs reopened
Reported by: | twilde | Owned by: | |
---|---|---|---|
Priority: | Medium | Milestone: | |
Component: | Obfuscation/Pluggable transport | Version: | |
Severity: | Normal | Keywords: | needs-spec-change, needs-tor-change |
Cc: | dmr | Actual Points: | |
Parent ID: | Points: | ||
Reviewer: | Sponsor: |
Description
We use SIGHUP to cause Tor to reopen its logs after a rotation, but currently this SIGHUP is not passed along to a managed proxy (ie obfsproxy). The only way to automatically tell obfsproxy to reopen logs without finding its process and sending a SIGHUP manually is to do a full tor restart, which will kill and restart the managed proxy as well. Perhaps all SIGHUPs to Tor should just be passed along to any (unchanged argument) managed proxies?
Child Tickets
Change History (7)
comment:1 Changed 5 years ago by
Keywords: | needs-spec-change needs-tor-change added |
---|---|
Type: | defect → task |
comment:2 Changed 4 years ago by
Parent ID: | → #16755 |
---|
comment:3 Changed 18 months ago by
Parent ID: | #16755 |
---|---|
Severity: | → Blocker |
comment:4 Changed 18 months ago by
Severity: | Blocker → Normal |
---|
comment:5 Changed 7 months ago by
Cc: | dmr added |
---|
comment:6 Changed 3 weeks ago by
Owner: | asn deleted |
---|---|
Status: | new → assigned |
asn does not need to own any obfuscation tickets any more. Default owners are trouble.
comment:7 Changed 2 weeks ago by
Status: | assigned → new |
---|
tickets were assigned to asn, setting them as unassigned (new) again.
Why does trac do that. Sigh.