[tor-dev] documenting reload vs. restart requirements per torrc option

[nusenu]

Hi,

I like unbound's documentation with this regards, for example they say
in their man page:

> The  interfaces  are not changed on a reload (kill -HUP)
>              but only on restart.


Could we add such information to every torrc option in the manual?


background: 

In relayor I need to reload/restart tor daemons on configuration changes
currently I blindly assume reload is fine, because in most cases it is
but it comes with the prices of accepting a certain level of error
since not all configuration changes can be applied by reloads.
To fix this I'd need to have authoritative information about
what changes require restarts vs. reloads.



[1] https://unbound.net/documentation/unbound.conf.html

-- 
https://twitter.com/nusenu_
https://mastodon.social/@nusenu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20180702/cc4d4c1c/attachment.sig>