[tor-bugs] #9732 [- Select a component]: Define SIGTERM behavior in pluggable transports spec

[Tor Bug Tracker & Wiki]

#9732: Define SIGTERM behavior in pluggable transports spec
----------------------------------+---------------------
 Reporter:  dcf                   |          Owner:
     Type:  defect                |         Status:  new
 Priority:  normal                |      Milestone:
Component:  - Select a component  |        Version:
 Keywords:                        |  Actual Points:
Parent ID:                        |         Points:
----------------------------------+---------------------
 https://gitweb.torproject.org/torspec.git/blob/2f031167c120761fa2a3ef3e1dc62e630ab7372a:/proposals/180
 -pluggable-transport.txt says:
   Proxies should respond to a single INT signal by closing their listener
 ports and not accepting any new connections, but keeping all connections
 open, then terminating when connections are all closed.  Proxies should
 respond to a second INT signal by shutting down cleanly.
 But it's silent on SIGTERM. When I `/etc/init.d/tor stop` on Debian,
 `torctl` kills the tor process with SIGTERM. I noticed because the super-
 proxy from comment:32:ticket:7167 starts subprocesses. It was properly
 killing the subprocesses on SIGINT, but not on SIGTERM.

 My proposed wording:
   Proxies should respond to a single TERM signal by closing their listener
 ports, closing all existing connections, and terminating.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9732>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online