Opened 7 years ago

Closed 6 years ago

Last modified 4 years ago

#9503 closed enhancement (implemented)

Mechanism to provoke an unscheduled heartbeat.

Reported by: nickm Owned by: rl1987
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay easy
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


On tor-talk, Lars Noodén suggests that we should have some way to get a heartbeat message when none is scheduled. Seems like a fine idea to me! All of the good signals seem to be taken though. (HUP, USR1, USR2). We could add it to HUP, but that wouldn't let you get *just* the heartbeat, given all the other stuff that HUP does.

We could add a controller-level signal, but that's not quite so convenient.

Once we're done bikeshedding the interface, the implementation should be simple.

Child Tickets

Change History (10)

comment:1 Changed 7 years ago by grarpamp

Seconding use of the controller for user driven i/o with Tor. Regardless of whether the output goes to log, controller, or both.

Noting a possible goof: lumping with current USR1 stats is closer to where it would go though, not HUP's reload/restart.

Bind (dns) is an example of log, control.

comment:2 Changed 7 years ago by nickm

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

comment:3 Changed 6 years ago by rl1987

Owner: set to rl1987
Status: newaccepted

comment:5 Changed 6 years ago by rl1987

Status: acceptedneeds_review

comment:6 Changed 6 years ago by rl1987

comment:7 Changed 6 years ago by asn

Patch looks reasonable to me.

comment:8 Changed 6 years ago by nickm

Resolution: implemented
Status: needs_reviewclosed

Merged both; thanks!

comment:9 Changed 4 years ago by teor

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

Milestone renamed

comment:10 Changed 4 years ago by nickm

Milestone: Tor: 0.3.???

Milestone deleted

Note: See TracTickets for help on using tickets.