[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #1955 [Tor Client]: Control protocol 'signal' event for when we get a hup, etc

#1955: Control protocol 'signal' event for when we get a hup, etc
-------------------------+--------------------------------------------------
 Reporter:  arma         |       Owner:                    
     Type:  enhancement  |      Status:  needs_review      
 Priority:  minor        |   Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client   |     Version:                    
 Keywords:  easy         |      Parent:                    
-------------------------+--------------------------------------------------
Changes (by special):

  * status:  new => needs_review


Comment:

 Attached a patch implementing this event.

 Implementing SHUTDOWN or HALT would require waiting for the control
 connections to cleanly close on exit. That is pretty far out of scope for
 this feature, so I documented those as missing.

 RELOAD is also slightly misleading. With ReloadTorrcOnSIGHUP, the event
 will still be sent, but the configuration is not reloaded (the other
 SIGHUP actions do take place). If this is a concern, one option would be
 to have both 'RELOAD' and 'HUP' as events.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1955#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs