Opened 7 years ago

Last modified 8 weeks ago

#5148 new task

SIGHUP managed proxies when logs reopened

Reported by: twilde Owned by: asn
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 (5)

comment:1 Changed 5 years ago by asn

Keywords: needs-spec-change needs-tor-change added
Type: defect → task

comment:2 Changed 3 years ago by yawning

Parent ID: → #16755

comment:3 Changed 13 months ago by yawning

Parent ID: #16755
Severity: → Blocker

comment:4 Changed 13 months ago by yawning

Severity: Blocker → Normal

Why does trac do that. Sigh.

comment:5 Changed 8 weeks ago by dmr

Cc: dmr added
Note: See TracTickets for help on using tickets.