[tor-bugs] #21818 [Core Tor/Tor]: tor's handling of SIGHUP considered harmful

[Tor Bug Tracker & Wiki]

#21818: tor's handling of SIGHUP considered harmful
----------------------------------+----------------------------------
 Reporter:  cypherpunks           |          Owner:  (none)
     Type:  defect                |         Status:  closed
 Priority:  Medium                |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor          |        Version:
 Severity:  Normal                |     Resolution:  fixed
 Keywords:  035-roadmap-proposed  |  Actual Points:
Parent ID:  #25510                |         Points:
 Reviewer:                        |        Sponsor:
----------------------------------+----------------------------------
Changes (by teor):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Now that #8195 and #17873 are closed, it looks like the remaining options
 for this ticket are:

 Replying to [ticket:21818 cypherpunks]:
 > ...
 > 2. try to fail gently when reloading the config (report errors to the
 log, but don't die. probably a lot more work for an incomplete solution.)

 If there are specific reload bugs that can be fixed, please open tickets
 for them. But in general, some users rely on tor exiting when the config
 is bad.

 > 3. make SIGHUP cause tor to re-parse the config, report any errors it
 can, but not actually use the new config *unless* it contains a special
 new directive like `AllowRuntimeConfigChange 1` (the documentation for
 which would of course discuss the myriad ways this could make tor exit).
 (this might be the best option?)

 We won't change the default for `__ReloadTorrcOnSIGHUP`, because some
 users rely on tor exiting when the config is bad.

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