Define SIGTERM behavior in pluggable transports spec
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.